Part Number Hot Search : 
MEH63XBA KDZ24V KDZ24V EP221 DG4052A AT45DB UGSP15D ONTROL
Product Description
Full Text Search
 

To Download 28500-DSH-002-C Datasheet File
  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
　
 

  Datasheet File OCR Text:
  28500-DSH-002-C mindspeed technologies ? october 2006 mindspeed proprietary and confidential cx28500 multichannel synchronous communications controller data sheet
28500-DSH-002-C mindspeed technologies ? ii mindspeed proprietary and confidential ordering information revision history model number package operating temperature cx28500ebg 35 mm tbga ?40 ? 85 c cx28500g-12* 35 mm tbga (rohs compliant) ?40 ? 85 c *the g in the part number indicat es that this is an rohs compliant package. re fer to www.mindspeed.com for additional informati on. revision level date description 500052a ? july 2001 created. 500052b ? february 2002 updated to revision b. 500052c ? july 2002 updated to revision c. 28500-dsh-002-a ? november 2002 formerly document number 500052d. 28500-dsh-002-b ? june 2004 updated and made various corrections. 28500-DSH-002-C ? october 2006 added rohs information. updated format.
28500-DSH-002-C mindspeed technologies ? iii mindspeed proprietary and confidential cx28500 multichannel synchronous communications controller the cx28500 is an advanced multichannel synchronous communications controller. it formats and deformats up to 1024 high- level data link control (hdlc) channels in a cmos integrated circuit. cx28500 operates at layer 2 of the open systems interconnection (osi) protocol reference model. it provides a comprehensive, high-density solution for processing of hdlc channels for internetworking applications such as frame relay, integrated services digital network (isdn), d- channel signaling, x.25, signaling system 7 (ss7), data exchange interface (dxi), inter system link protocol (islp), and lan/wan data transport. under minimal host supervision, cx28500 manages table-like data structures of channel data buffers in host memory by performing direct memory access (dma) of up to 1024 channels. cx28500 interfaces to 32 independent serial data streams, such as t1/e1 signals. it then transfers data across the popular 32-bit or 64-bit peripheral component interface (pci) bus to system memory at a rate up to 66 mhz. the cx28500 has an aggregate data throughput of 390 mbps. each serial interface can be operated up to 13.0 mhz. six serial interfaces can be operated at rates up to 52 mhz. logical channels can be mapped as any combination of digital signal level 0 (ds0) time slots to support isdn hyperchannels (n x 64 kbps). additionally, logical channels can operate in subchanneling mode (n x 8 kbps) by mapping a combination of ds0 time slots and/or the individual bits of a ds0 time slot (8 bits). for example, a 56 kbps channel can be achieved by mapping 7 bits out of 8 possible bits in a time slot (7 x 8 kbps = 56 kbps). cx28500 also includes a 32-bit expansion port for bridging the pci bus to local microprocessors or peripherals. a joint test action group (jtag) port enables boundary- scan testing to replace bed-of-nails board testing. functional block diagram host interface (pci) device configuration registers pci interface pci configuration space (function 0) rxdma and txdma serial interface unit (siu) rx line processor rslp tx line processor tslp tsbus or pcm highway exp bus jtag test access 31 0 pci bus local bus physical interface distinguishing features 1024-channel hdlc controller osi layer 2 protocol support general purpose hdlc (iso 3309) x.25 (lapb) frame relay (lapf/ansi t1.618) isdn d-channel (lapd/q.921) islp support 32 independent serial interfaces, which support: mixed data rates (c ombination of t1/e1/ t3/e3, etc.) as long as they do not exceed each port?s respective bandwidth limitation and the overall device bandwidth of 390 m bps per direction 32 t1/e1 data streams 6 hssi interfaces (52 mbps) dc to 13.0 mbps serial interfaces 32 x 8.192 mhz tdm busses configurable logical channels standard ds0 (56, 64 kbps) subchanneling (n x 8 kbps) hyperchannel (n x 64 kbps) unchannelized mode per-channel protocol mode selection non-fcs mode 16-bit fcs mode 32-bit fcs mode transparent mode (unformatted data) hardware flow control (cts) selectable endian configuration on data per-channel dma buffer management table-like data structures variable size transmit/receive fifo per-channel message length check select no length checking select from three 14 -bit registers to compare message length direct pci bus interface 32/64-bit, 33/66 mhz operation bus master and slave operation pci version 2.1 host back-to-back transaction over the pci hssi interfaces (52 mbps) local expansion bus interface (ebus) 32-bit multiplexed address/data bus tsbus support of 64-bit ecc host memory low power, 3.3 v cmos operation jtag boundary scan access port 35 mm x 35 mm 580-pin bga available in green (roh s compliant) as well as standard version
28500-DSH-002-C mindspeed technologies ? iv mindspeed proprietary and confidential table of contents table of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv list of figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi list of tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii 1.0 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 cx28500?s operational modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 1.2 cx28500 serial port throughput limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 1.3 cx28500?s bus interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 1.3.1 pci?peripheral components interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 1.3.2 ebus?local expansion bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 1.3.3 tsbus?time slot bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 1.4 cx28500 layering model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 1.5 cx28500?s applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 1.6 cx28500 applications examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 1.6.1 t1/t3 wan access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 1.6.2 t3/e3 frame relay switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 1.6.3 128 port dsl access concentrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 1.6.4 sonet/sdh mapper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 1.6.5 line card sonet/atm sar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 1.7 feature summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 1.8 system overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 1.9 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 1.10 receive data path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 1.11 transmit data path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 1.12 pin configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 1.13 cx28500 hardware sign als description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 2.0 internal architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.1 serial interface unit (siu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 2.2 serial line processor (slp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 2.3 direct memory access controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 2.3.1 general feature list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 2.4 interrupt controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 3.0 host interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3.1 pci interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
table of contents 28500-DSH-002-C mindspeed technologies ? v mindspeed proprietary and confidential 3.1.1 pci initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 3.1.2 pci bus operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 3.1.3 fast back-to-back transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 3.1.3.1 operation mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 3.1.3.2 example of an arbitration for fast back-to -back and non-fast back-t o-back transactions . .43 3.1.4 pci configuration space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 3.2 pci configuration registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 3.2.1 pci master and slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 3.2.1.1 register 0, address 00h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 3.2.1.2 register 1, address 04h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 3.2.1.3 register 2, address 08h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 3.2.1.4 register 3, address 0ch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 3.2.1.5 register 4, address 10h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 3.2.1.6 register 5?14, address 14h?38h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 3.2.1.7 register 15, address 3ch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 3.2.2 pci reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 3.2.3 pci throughput and latency considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 3.2.4 host interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 4.0 expansion bus (ebus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.1 ebus?operational mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 4.1.1 initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 4.1.2 clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 4.1.3 interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 4.1.4 address duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 4.1.5 data duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 4.1.6 bus access interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 4.1.7 pci to ebus interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 4.1.8 microprocessor interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 4.1.9 arbitration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 4.1.10 connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 4.1.10.1 multiplexing address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 5.0 serial interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 5.1 serial port interface definition in conventional mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 5.1.1 frame synchronization flywheel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 5.1.2 change of frame alignment (cofa) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 5.1.3 out of frame (oof)/frame recovery (frec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 5.1.4 general serial port interrupt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 5.1.5 channel clear to send (cts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 5.1.6 frame alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 5.1.7 polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 5.2 serial port interface definition in tsbus mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 5.2.1 tsbus frame synchronization flywheel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 5.2.2 tsbus change of frame alignment (cofa) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 5.2.3 tsbus out of frame (oof)/frame recover y (frec). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 5.2.4 tsbus frame alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
table of contents 28500-DSH-002-C mindspeed technologies ? vi mindspeed proprietary and confidential 5.2.5 tsbus polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 5.2.6 tsbus channel clear to send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 5.2.7 tsbus interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 5.2.8 payload tsbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 5.2.9 overhead tsbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 5.2.9.1 overhead data channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 5.2.9.2 tsbus time slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 6.0 memory organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 6.1 memory architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 6.1.1 register map and shared memory access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 6.2 global registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 6.2.1 service request mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 6.2.1.1 service request descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 6.2.1.2 service request descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 6.2.2 port alive registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 6.2.3 soft chip reset register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 6.2.4 general pci note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 6.3 interrupt level descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 6.3.1 interrupt queue descr iptor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 6.3.1.1 interrupt descr iptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 6.3.1.2 interrupt status descrip tor register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 6.3.1.3 interrupt handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 6.4 global configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 6.5 ebus configuration register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 6.6 receive path registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 6.6.1 rslp channel status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 6.6.2 rslp channel configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 6.6.3 rdma buffer allocation register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 6.6.4 rdma configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 6.6.5 rsiu time slot configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 6.6.5.1 time slot map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 6.6.5.2 rsiu time slot configuration descrip tor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 6.6.6 rsiu time slot pointer allocation register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 6.6.6.1 time slot allocation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 6.6.7 rsiu port configuration register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 6.6.8 rslp maximum message length register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 6.7 transmit path registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 6.7.1 tslp channel status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 6.7.2 tslp channel configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 6.7.3 tdma buffer allocation register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 6.7.4 tdma configuration register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 6.7.5 tsiu time slot configuration register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 6.7.5.1 time slot map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 6.7.5.2 tsiu time slot configur ation descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 6.7.6 tsiu time slot pointer assignment register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
table of contents 28500-DSH-002-C mindspeed technologies ? vii mindspeed proprietary and confidential 6.7.6.1 time slot allocation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 6.7.7 tsiu port configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 6.8 receive and transmit data stru ctures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 6.8.1 transmit message path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 6.8.1.1 shared memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 6.8.2 receive message path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 6.8.2.1 shared memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 6.8.3 internal memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 6.8.3.1 transmit path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 6.8.3.2 receive path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 6.8.4 head pointer table and its content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 6.8.5 message descriptor (md) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 6.8.6 buffer descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 6.8.7 buffer status descriptor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 6.8.8 data buffer pointer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117 7.0 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 7.1 initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 7.1.1 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 7.1.1.1 hard pci reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 7.1.1.2 soft chip reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120 7.1.2 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120 7.1.2.1 pci configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120 7.1.2.2 service request mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 7.1.2.3 global and ebus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 7.1.2.4 interrupt queue configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 7.1.2.5 channel and port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 7.1.2.6 typical initialization procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 7.2 channel operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 7.2.1 channel activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 7.2.1.1 transmit channel activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 7.2.1.2 receive channel activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 7.2.2 channel deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 7.2.2.1 transmit channel deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 7.2.2.2 receive channel deactivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 7.2.3 channel jump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 7.2.3.1 receive channel jump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 7.2.3.2 transmit channel jump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 7.2.4 channel reactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 7.2.5 unmapped time slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 8.0 basic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 8.1 protocol-independent operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 8.1.1 transmit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 8.1.2 receive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 8.2 hdlc mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
table of contents 28500-DSH-002-C mindspeed technologies ? viii mindspeed proprietary and confidential 8.2.1 frame check sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130 8.2.2 opening/closing flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130 8.2.3 abort codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 8.2.4 zero-bit insertion/deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 8.2.5 message configuration bits?hdlc mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 8.2.5.1 idle code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 8.2.5.2 inter-message pad fill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 8.2.5.3 ending a message with an abort or sending an abort sequence . . . . . . . . . . . . . . . . . . . . .132 8.2.6 transmit events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 8.2.6.1 end of buffer [eob] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 8.2.6.2 end of message [eom] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 8.2.6.3 abort termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 8.2.7 receive events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 8.2.7.1 end of buffer [eob] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 8.2.7.2 end of message (eom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 8.2.7.3 change to abort code (chabt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 8.2.7.4 change to idle code (chic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 8.2.7.5 frame recovery (frec) or generic serial port (sport) interrupt . . . . . . . . . . . . . . . . . .134 8.2.7.6 receive cofa recovery (rcrec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 8.2.8 transmit errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 8.2.8.1 transmit underrun [buff] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 8.2.8.2 transmit change of frame alignment (cofa) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 8.2.8.3 transmit cofa recovery (tcrec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 8.2.9 receive errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 8.2.9.1 receive overflow [buff] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 8.2.9.2 receive change of frame alignment (cofa) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 8.2.9.3 out of frame (oof) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138 8.2.9.4 frame check sequence (fcs) error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138 8.2.9.5 octet alignment error (align). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 8.2.9.6 abort termination (abt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 8.2.9.7 long message (lng) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 8.2.9.8 short message (sht). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 8.3 transparent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 8.3.1 message configuration bits?tra nsparent mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 8.3.1.1 idle code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 8.3.1.2 inter-message pad fill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 8.3.1.3 ending a message with an abort or sending an abort sequence . . . . . . . . . . . . . . . . . . . . .141 8.3.2 transmit events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 8.3.2.1 end of buffer [eob] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 8.3.2.2 end of message [eom] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 8.3.3 receive events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 8.3.3.1 end of buffer [eob] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 8.3.3.2 end of message (eom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 8.3.3.3 frame recovery (frec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
table of contents 28500-DSH-002-C mindspeed technologies ? ix mindspeed proprietary and confidential 8.3.3.4 receive cofa recovery (rcrec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143 8.3.4 transmit errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143 8.3.4.1 transmit underrun [buff] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143 8.3.4.2 transmit change of frame alignment (cofa) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144 8.3.5 receive errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144 8.3.5.1 receive overflow [buff] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144 8.3.5.2 receive change of frame alignment (cofa) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145 8.3.5.3 out of frame (oof) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145 8.3.5.4 short cofa (sht cofa). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 9.0 self-servicing buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 10.0 electrical and mechanical spec ification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 10.1 electrical and environmental specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 10.1.1 absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 10.1.2 recommended operating conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 10.1.3 electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 10.1.4 power-up sequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 10.2 timing and switching specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 10.2.1 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 10.2.2 host interface (pci) timing and switching characteristic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 10.2.3 expansion bus (ebus) timing and switch ing characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 10.2.4 ebus arbitration timing specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157 10.2.5 serial interface timing and switching characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 10.2.6 test and diagnostic interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 10.3 package thermal specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165 10.4 mechanical specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 appendix a: cx28500 pci bus latency and uti lization analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 a.1 objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167 a.2 definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167 a.3 assumptions/modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 a.4 pci transaction timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 a.4.1 read. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 a.4.2 write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 a.5 receive messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 a.6 transmit messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 a.7 allocation of internal slp buffer (fifo) space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 a.8 maximum feasible pci latency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 a.9 maximum endurable latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170 a.10 pci bus utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171 a.11 maximum tolerable delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 a.12 other considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 a.13 summary and explanation of terms used in calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 a.14 examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 a.15 differences in the combined t1 payload and overhead table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
table of contents 28500-DSH-002-C mindspeed technologies ? x mindspeed proprietary and confidential appendix b: example of an arbitr ation for fast back-to-back and n on-fast back-to-back transactions. 182 appendix c: t3 frame relay switch application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 appendix d: example of little-big endian byte ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 appendix e: tsbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 e.1 connection between cx28500 and other tsbus device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 e.1.1 vsp mapping of intermixed digital level 2 signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 e.2 timing details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 e.2.1 payload bus, ac characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 e.2.2 transmit timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198 e.2.3 receive timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199 e.3 overhead bus, ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 e.3.1 transmit timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 e.3.2 receive timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 e.4 dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 appendix f: notation, acronyms, abbreviati ons, and definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 f.1 radix notation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 f.2 bit stream convention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 f.3 acronyms, abbreviations, and definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 f.3.1 acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 f.3.2 definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 appendix g: scope of spec ification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 g.1 applicable specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
28500-DSH-002-C mindspeed technologies ? xi mindspeed proprietary and confidential list of figures figure 1-1. cx28500 as a data link layer device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 figure 1-2. mid-range router application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 figure 1-3. high-range router application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 figure 1-4. dslam or iad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 figure 1-5. gigabit router line card for oc-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 figure 1-6. line card sonet/atm sar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 figure 1-7. system overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 figure 1-8. cx28500 top level block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18 figure 1-9. pin configuration diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21 figure 2-1. serial interface functional block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36 figure 3-1. host interface functional block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41 figure 3-2. address lines during configuration cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44 figure 4-1. ebus functional block diagram with local mpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51 figure 4-2. ebus functional block diagram without local mpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52 figure 4-3. ebus connection, non-multiplexed ad dress/data, 8 framers, no local mpu . . . . . . . . . . . . . . . . . . . . . . . . . 4-57 figure 4-4. ebus connection, non-mu ltiplexed address/data, 16 framers, no local mpu . . . . . . . . . . . . . . . . . . . . . . . . 4-58 figure 4-5. ebus connection, multip lexed address/data, 8 framers, no local mpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59 figure 4-6. ebus connection, multip lexed address/data, 4 framers, no local mpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59 figure 5-1. rdma state machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64 figure 5-2. tdma state machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65 figure 5-3. tsbus number of time slots into a payload or overhead frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69 figure 6-1. interrupt notification to host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89 figure 6-2. transmit data structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-108 figure 6-3. receive message data structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-109 figure 10-1. pci clock (pclk) waveform, 3.3 v clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-152 figure 10-2. pci output timing waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-154 figure 10-3. pci input timing waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-154 figure 10-4. ebus reset timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-155 figure 10-5. ebus output timing waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-156 figure 10-6. ebus input timing waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-156 figure 10-7. ebus write/read cycle, intel-style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-157 figure 10-8. ebus write/read cycle, motorola-style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-158
list of figures 28500-DSH-002-C mindspeed technologies ? xii mindspeed proprietary and confidential figure 10-9. serial interface clock (rclk,tclk) waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-159 figure 10-10. serial interface data input waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-160 figure 10-11. serial interface data delay output waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-161 figure 10-12. transmit and receive t1 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-162 figure 10-13. transmit and receive channelized non t1 (i.e., n x 64) mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-163 figure 10-14. jtag interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-164 figure 10-15. 580-pin bga package diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-166 figure b-1. pci burst write: two 64-bit fast back-to-back transactions to same target . . . . . . . . . . . . . . . . . . . . . . . . . b-182 figure b-2. pci burst write: two 32-bit fast back-to-back transactions to same target . . . . . . . . . . . . . . . . . . . . . . . . . b-183 figure b-3. pci burst read: two 64-bit transact ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . b-184 figure b-4. pci burst: two 32-bit transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . b-185 figure b-5. pci burst write followed by burst read: fast back-to-back to same target . . . . . . . . . . . . . . . . . . . . . . . . . b-186 figure b-6. pci burst read followed by burst write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . b-187 figure c-1. high-end router application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . c-188 figure c-2. ds3/e3 line unit interface connect ion with t3/e3 framer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . c-189 figure c-3. t3/e3 framer connection with hdlc controller (t3/e3 payl oad path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . c-189 figure c-4. t3/e3 framer connection with hdlc controller (t3/e3 over head path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . c-190 figure e-1. cx28500 time slot interface pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-193 figure e-2. source/destination of tsbus block line-side signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-195 figure e-3. payload time slot bus transmit data (tsb_tdat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-198 figure e-4. payload time slot bus transmit stuff indicator (tsb_ts tuff) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-199 figure e-5. payload time slot bus receive data (tsb_rdat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-200 figure e-6. payload time slot bus receive stu ff indicator (tsb_rstuff) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-200
28500-DSH-002-C mindspeed technologies ? xiii mindspeed proprietary and confidential list of tables table 1-1. supported serial port modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 table 1-2. allowed cx28500 port configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 table 1-3. data path combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 table 1-4. examples of serial port configurations with 33 mhz pci clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 table 1-5. examples of serial port configurations with 66 mhz pci clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 table 1-6. pin description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22 table 1-7. i/o pin types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28 table 1-8. cx28500 hardware signal definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29 table 3-1. pci configuration space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44 table 3-2. register 0, address 00h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45 table 3-3. register 1, address 04h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46 table 3-4. register 2, address 08h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48 table 3-5. register 3, address 0ch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48 table 3-6. register 4, address 10h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49 table 3-7. register 5-14, address 14h?38h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49 table 3-8. register 15, address 3ch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49 table 4-1. ebus service request descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53 table 4-2. ebus service request field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53 table 6-1. pci register map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71 table 6-2. indirect register map address accessible via service requ est mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71 table 6-3. service request length register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73 table 6-4. service request pointer register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73 table 6-5. service request descripto r?opcode description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74 table 6-6. device configuration descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76 table 6-7. device configuration field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76 table 6-8. ebus configuration serv ice request descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77 table 6-9. field descriptions of ecd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77 table 6-10. channel configur ation service request descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78 table 6-11. fields description of ccd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78 table 6-12. receive port alive register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79 table 6-13. transmit port alive register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79 table 6-14. interrupt queue descrip tor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81
list of tables 28500-DSH-002-C mindspeed technologies ? xiv mindspeed proprietary and confidential table 6-15. interrupt queue pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81 table 6-16. interrupt queue length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81 table 6-17. dma interrupt descriptors format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83 table 6-18. non-dma interrupt descr iptors format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84 table 6-19. interrupt status descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86 table 6-20. global configuration descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89 table 6-21. ebus configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-91 table 6-22. rslp channel status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92 table 6-23. rslp channel configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92 table 6-24. rdma buffer allocation register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94 table 6-25. rdma channel configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94 table 6-26. rsiu time slot configuration d escriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96 table 6-27. rsiu time slot pointer allocation register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-97 table 6-28. rsiu port configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-97 table 6-29. maximum message length register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-100 table 6-30. tslp channel status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-100 table 6-31. tslp channel configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-101 table 6-32. tdma buffer allocation register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102 table 6-33. tdma channel configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102 table 6-34. tsiu time slot configuration descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-104 table 6-35. tsiu time slot pointers register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-105 table 6-36. tsiu port configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-105 table 6-37. transmit and receive b ase address head pointer (tbahp and rbahp) content . . . . . . . . . . . . . . . . . . . . . . 6 -111 table 6-38. transmit and receive he ad pointer table (thpt and rhpt) content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-111 table 6-39. transmit or receive message descrip tor table (tmdt) or (rmdt) content . . . . . . . . . . . . . . . . . . . . . . . . . 6-112 table 6-40. transmit buffer descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-113 table 6-41. receive buffer descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-114 table 6-42. transmit buffer status descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-115 table 6-43. receive buffer status descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116 table 6-44. data buffer pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-117 table 6-45. data buffer pointer in pch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-118 table 10-1. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-149 table 10-2. recommended 3.3 v operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-150 table 10-3. dc characteristics for 3.3 v operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-150 table 10-4. pci interface dc specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-151 table 10-5. pci clock (pclk) waveform parameters, 3.3 v clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-152 table 10-6. pci reset parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-153 table 10-7. pci input/output timing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-153 table 10-8. pci i/o measure conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-153 table 10-9. ebus reset parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-155
list of tables 28500-DSH-002-C mindspeed technologies ? xv mindspeed proprietary and confidential table 10-10. ebus input/output timing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-155 table 10-11. ebus input/output measure conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-156 table 10-12. serial interface clock (rclk, tclk) parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-159 table 10-13. serial interface input/output timing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-159 table 10-14. serial interface input/output measu re conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-160 table 10-15. test and diagnostic interface timing requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-164 table 10-16. test and diagnostic interface swit ching characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-164 table 10-17. cx28500 package thermal resistan ce characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-165 table a-1. configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-173 table a-2. suggestions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-173 table a-3. calculated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-173 table a-4. including spare time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-174 table a-5. non ??spare time? calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-175 table a-6. example one . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-176 table a-7. example two . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-177 table a-8. example three . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-180 table d-1. little endian . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . d-191 table d-2. big endian . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . d-191 table e-1. system side interface: payload time slot bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-193 table e-2. system side interface: overhead time slot bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-194 table e-3. system side interface: overhead ti me slot bus frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-195 table e-4. vsp mapping of intermixed digital level 2 signals contai ning either ds1 or e1 signals . . . . . . . . . . . . . . . . e-196 table e-5. transmit timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e-199
28500-DSH-002-C mindspeed technologies ? 1 mindspeed proprietary and confidential 1.0 introduction the cx28500 hdlc controller (cx28500) is a 1024-channel communications controller that operates at layer 2 of the open system interconnection (osi) protocol reference. it provides a comprehensive, high density solution for hdlc channels for internetworking applications.  hdlc/sdlc  lapb, lapd  digital access cross-connect (dac)  frame relay switches and access devices (frad)  isdn-d channel signalling x.25  smds/atm dxi  lan/wan access data  sonet/sdh add/drop multiplexers (adms)  terminal multiplexers (tms)  high range/gigabit routers cx28500 interfaces to 32 independent serial data streams such as t1/e1, t3/e3, sts-1/stm-1, and ds3. it signals and transfers data across the high performance 32/64-bit peripheral component interface (pci) bus to system memory at a rate up to 66 mhz. each serial port can be configured to support different types of interfaces. all of the cx28500?s serial ports are individually programmable to operate as conventional or tsbus serial ports.
introduction 28500-DSH-002-C mindspeed technologies ? 2 mindspeed proprietary and confidential 1.1 cx28500?s operational modes ta bl e 1 - 1 explains the cx28500?s supported serial port mode. table 1-1. supported serial port modes cx28500 serial port modes description conventional unchannelized (1) in this mode, transmit synchroni zation (tsync) and recei ve synchronization (rsync) are ignored. the serial input/output data stream is a bit-stream without framing or alignment. the bit-stream belongs to a single logical channel. the cx28500 conventional, unchannelized mode can operate up to 13 mbps for all 32 serial ports. the first six ports can operate unchanneliz ed t3/e3, hssi, or sts-1/stm-1 bit-stream up to 52 mbps per serial interface (for reference, see section 1.2 ). conventional channelized (1)(2) the serial bit-stream is treated as a frame of n time slots (where n is less than or equal to 4096, given that other restrictions are met). the m aximum bandwidth embedded into the pcm highway for the first six ports is sts-1 rate (51.84 mbps). the byte and frame synch ronization performed is based on receive and transmit sync pulse (rsync and tsync). (for a deta iled description of these signals, see chapter 5.0 .) conventional t1 mode (1) the serial bit-stream is treated as a frame of n time slots (where n has the same meaning as in channelized mode). if the serial port is configured in t1 mode then the port operates according to the t1 framing definition (i.e., 24 time slots, where the first bit is the f-bit). the difference between channelized mode and t1 mode is that in t1 mode, the f-bit of the t1 fr ame is masked off and is dropped on input, and is generated for the output (for proper timing only?a t1 fr amer is needed to generate the correct f-bit). tsbus (2)(3) the tsbus serial interface bit-stream is treated as a frame of n time slots (where n is defined as greater than or equal to 6, and the aggregate number of time slots across all ports in any direction does not exceed the 4096 available time slots in each direction, receive or transmit) or variable bandwidth time slots called virtual serial ports (vsps). byte synchronization and frame synchronization is performed based on the tsbus sync pulse stb (i.e., bus strobe). mixed t1/e1 paths in one t3, mixed vt1.5/vt2 paths mapped to vtgs in one sts1, and mixed vc11/vc12 paths mapped to tug2 in stm-1 are allowed using this serial port configuration. footnote: (1) a conventional serial port is defined as se ven input/output si gnals as follows: transmit clock (tclk), transmit synchronization (tsync), transmit data (tdat), receive clock (rclk) , receive synchronization (rsyn c), receive data (rdat), receive out-of-frame, or clea r to send (roof/ cts). (for a detaile d description of these signals, see section 2.1 .) (2) channelized mode refers to a data bit stream segmented into frames. each frame c onsists of a series of 8-bit time slots. the fr ame synchronization is maintained in both the tr ansmit and receive direction by using the transmit synchronizati on (tsync) and rece ive synchronization (rsync) input signals. (3) a time slot bus (tsbus) is defi ned as seven input/output signals as follows: transmit clock (tcl k), transmit stuff (tstuff), tr ansmit data (tdat), strobe (stb), receive clock (r clk), receive stuff (rstuff), receive data (rdat). (for a detailed description of th ese signals, see chapter 5.0 ).
introduction 28500-DSH-002-C mindspeed technologies ? 3 mindspeed proprietary and confidential 1.2 cx28500 serial port throughput limits each of the cx28500 serial ports can be configured to operate in any of the preceding operational modes. the following restrictions apply: 1. the overall number of time slots cannot exceed 4096. 2. the overall number of channels cannot exceed 1024. 3. only the first 6 ports can be configured to operate as high speed ports?t3 (44.7 mbps), e3 (34.4 mbps), and hssi (52 mbps). 4. the total accumulated data rate of all serial port clocks in either receive or transmit direction must be less than 250 mbps for a pci bus rate of 33 mhz and 390 mbps for a pci bus rate of 66 mhz. allowed cx28500 port configurations are represented in ta b l e 1 - 2 . table 1-2. allowed cx28500 port configurations speed of port 4 mbps 8 mbps 13 mbps 34.4 mbps 44.7 mbps 51.8 mbps number of ports 32 32 32 6 (1) 6 (1) 6 (1) footnote: (1) for high speed ports such as t3 (44.736 mbps), e3 (34.368 mbps), hssi (51.840 mbps) th e data path of the remaining ports may operate at less than or equa l to 4 mbps or 8 mbps (see table 1-3 ).
introduction 28500-DSH-002-C mindspeed technologies ? 4 mindspeed proprietary and confidential cx28500?s configuration options are extremely flexible. each logical channel can be assigned to a physical stream ranging from 8 kbps (sub-channeling mode) to 52 mbps. cx28500?s serial ports can interface to a standard pcm highway or tsbus bus, which can be configured to operate at any of the serial port rates given in tables 1-4 and 1-5 . table 1-3. data path combinations path combinations low speed high speed aggregate port speed 2 mbps (2.048) 4 mbps (4.096) 8 mbps (8.192) 10 mbps (10.240) 13 mbps (12.960) 34.4 mbps (1) ( e3-34.368 ) 44.7 mbps (1) (t3-44.736) 51.8 mbps (1) (hssi-51.840) allowed number of ports ?17 ? ? ? ? ? 6 380.7 mbps ?26 ? ? ? 6 ? ? 312.7 mbps ?? 14 ? ? ? 6 ? 383.1 mbps ?? 22 ? ? 6 ? ? 386.4 mbps ? ? 9 ? ? ? ? 6 384.8 mbps ?? ? 11 ? ? 6 ? 381.1 mbps ? ? ? 7 ? ? ? 6 382.7 mbps ?? ? 17 ? 6 ? ? 380.3 mbps ? ? ? ? 9 ? 6 ? 385.1 mbps ? ? ? ? 6 ? ? 6 388.8 mbps ?? ? ? 14 6 ? ? 387.6 mbps 26 ? ? ? ? ? 6 ? 321.7 mbps 26 ? ? ? ? ? ? 6 364.3 mbps 26 ? ? ? ? 6 ? ? 259.5 mbps general note: 1. these data path combinat ions are meant to illustrate the flexibility in data path configur ation, and are not suggesting that these are the only supported configurations. again, they ar e here for illustration purposes only. othe r data rates and path combinations are achievable, as long as device-aggregate band width restrictions and per-port bandwidth restrictions are met. footnote: (1) a high speed port can be e3 (34.4 mbps), t3 (4 4.7 mbps), or hssi (52 mbps) without ex ceeding the maximum of six serial ports. table 1-4. examples of serial port c onfigurations with 33 mhz pci clock configuration total bandwidth pci clock 32 x t1 49.408 mbps 33 mhz 32 x e1 65.536 mbps 33 mhz 2 x 52 + 30 x e1 165.44 mbps 33 mhz 32 x 2e1 131.072 mbps 33 mhz maximum 250 mbps 33 mhz
introduction 28500-DSH-002-C mindspeed technologies ? 5 mindspeed proprietary and confidential the send and receive data can be formatted in the hdlc messages or left unformatted (transparent mode) over any combination of bits within a selected time slot. cx28500?s protocol message type is specified on a per-channel basis. 1.3 cx28500?s bus interfaces 1.3.1 pci?peripheral co mponents interface an on-device pci 2.1 compliant controller, known as the host interface, is provided. access to cx28500 is available through pci read, write, and configuration cycles. the pci bus interface supports dma bursts for extremely high message throughput applications, up to 780 mbps of the aggregate serial port bandwidth (i.e., 390 mbps per direction). 1.3.2 ebus?local expansion bus the cx28500 provides an on-device 32-bit local expansion bus (ebus) controller that allows a host processor to access peripheral memory space on the ebus. physical devi ces interface directly to cx28500 over the pci using the configurable memory mapping features. although ebus utilization is optional, the most notable application for the eb us is the connectio n to peripheral devices (e.g., cx28365, a 12-port t3/e3 framer) local to cx28500?s serial ports. 1.3.3 tsbus?time slot bus cx28500 provides a tsbus interface for variable bandwidth time slots, virtua l serial port (vsp). a vsp is defined as an entity?quantified by clock bus rate divided by number of time slots?which provides multiple asynchronous paths over a single se rial port. a programmable number of vsps per ts bus are allowed by using the existing start and end address time slot pointer mechanism. the pointer mechanism allows cx28500 to allocate any number of vsps on a given serial port, providing that the total number of vsps alloca ted across all ports does not exceed 4096, the total number of logical channels does not exceed 1024, and the serial port clock speed does not exceed 52 mhz. while operating in tsbus mode, the minimum numb er of time slots required is 8 per serial port. the programmable number of time slots, implemented by the pointer mechanism (i.e., configurable start and end table 1-5. examples of serial port c onfigurations with 66 mhz pci clock configuration total bandwidth pci clock 4 x 52 208 mbps 66 mhz 32 x 10 320 mbps 66 mhz 6 x 52 + 6 x 13 390 mbps (1) 66 mhz 32 x 4e1 262.144 mbps 66 mhz 4 x 52 + 28 x t1 251.232 mbps 66 mhz 6 x t3 + 26 x t1 310 mbps 66 mhz 26 x 8 + 4 x t3 387 mbps 66 mhz maximum 390 mbps 66 mhz general note: sts-1 data rates (51.84mbps) are achieved when used in combination with the m29503 over the tsbus. footnote: (1) half of the oc-12 data rate, including overhead.
introduction 28500-DSH-002-C mindspeed technologies ? 6 mindspeed proprietary and confidential addresses) allows any number of vsps to be concaten ated into a single logical chan nel. this concatenation allows mixed vtg path options without changing the number of time slots assigned to the tsbus port. in the tsbus transmit direction, cx28500 requires the stuff status for each time slot to be presented at its tstuff input exactly 8 time slots in advance of the actual time slot for whic h the stuff status is applied. the amount of the tstuff advance is fixed at 8 time slots even though the number of time slots within a frame might vary. for the receive direction cx28500 requires the stuff status for each time slot to be presented at its rstuff input on the current time slot for which the stuff is applied (for a detailed description, see the timing diagrams in appendix e .) 1.4 cx28500 layering model independent of the particular layering scheme used, or the functions of the layers, the operation of layered protocols is based on the fundamental idea of a layering principle (refer to figure 1-1 ). level 2 of the protocol stack specifies how data travels between a host and the packet switch to which it connects. because raw hardware delivers only a stream of bits, the level 2 protocol must define the format of frames and specify how the machines recognize frame boundaries. this function is one of cx28500?s features, including error detection (e.g., a frame checksum). usually, protocols use the term ?frame? to refer to a unit of data as it passes between a host and a packet switch. cx28500, as a high-throughout communications controlle r for synchronous or asynchronous path applications, multiplexes and demultiplexes up to 1024 data channels and allows upper protocols to recognize frame boundaries and check if a frame has been transferred successfully. examples of cx28500?s potential applications as a layer 2 protocol device and examples of device communication with other upper layers are described in section 1.5 . figure 1-1. cx28500 as a data link layer device - hssi - sonet/sdh - t3/e3 - t1/e1 - x.25 - modems/dsl - variable speed per channel port - variable number of time slots per port - variable number of channels per port - variable number of time slots per logical channel - packet switch - cell switch - processor physical layer link layer upper layer ebus tsbus pcm highway pci cx28500 features 500052_078
introduction 28500-DSH-002-C mindspeed technologies ? 7 mindspeed proprietary and confidential 1.5 cx28500?s applications the potential applications for cx28500 are in data communications and telecommunications markets, such as the following:  wan access equipment router  remote access server  frame relay switch  isdn basic-rate (bri) or primary-rate interfaces (pri)  edge switch (atm or frame relay)  protocol converter  enterprise switch (frame relay or atm)  sonet/sdh packet switches  high-range router /gigabit router  transmission equipment  digital access cross-connects (dacs)  digital loop carries (dlcs)  wireless communication  cellular base station controllers
introduction 28500-DSH-002-C mindspeed technologies ? 8 mindspeed proprietary and confidential 1.6 cx28500 applications examples 1.6.1 t1/t3 wan access an example of a mid-range router application for channelized ds3 and unchannelized/channelized ds1 line interface is illustrated in figure 1-2 . the block diagram illustrates how the cx2850 0 interconnects with 3 different buses:  pci bus used for communication between cx28500, central host processor and shared memory.  ebus used for communication with peripheral devices.  tsbus used to provide multiple asynchronous paths between the ds3 framers and the central host processor. the tsbus also provides paths for inter-processor control (ipc) channels between the ds3 framers and the central host processo r. this example illustrates how 30 of cx28500?s 32 serial ports are used in a mid-range router application. the t3/e3 data path (payload) occupies only one tsbus port and the overhead path occupies another tsbus port.  feature list: figure 1-2. mid-range router application cx28333 liu host sm cx29503 ds3 signals cx28398 framers cx28380 cx28500 t1 signals t1 4 1 2 7 channelized t3 t1 t1 t1 t1 signals t1 0 t1 27 . . . . . . . . . . . . b r i d g e pci pci ebus ebus 28ds1 overhead tsbus tsbus 28ds1 payload (channelized or unchannelized t1) 500052_079 legend: cx28333-ds3/e3 line interface unit. cx29503?m13 framers; 28 ds1 signals can be multiplexed into and demultiplexed from 1 ds3 signal or various combinations of e1 and ds1 signals that can be multiplexed into and demultiplexed from 1 ds3 signal. 7xcx28380?t1/e1 line interface unit. 4xcx28398 or 2xcx28395?t1/e1/framers. cx28500?hdlc controller. general note: the application handles t1/e1 and t3/e3 signals both in north american digital telephony hierarchy and in the european digital telephony hierarchy.
introduction 28500-DSH-002-C mindspeed technologies ? 9 mindspeed proprietary and confidential  30 ports  pci bus that operates to redirect packets from and to local ram via a pci bridge  ebus that provides a path of control and performance monitoring for local devices  two tsbus ports that provide the path for 28 ds1 payload data and 28 ds1 overhead data as a mixed combination of asynchronous paths  simultaneous connection of cx28500?s serial port modes, including channelized tsbus mode and t1/e1, either channelized or unchannelized  variable speed per port and channel  configurable allocation of the time slots  sufficient bandwidth to perform 28 ds1 paths and 1 ds3 path simultaneously  low cost and powerful line card interface  high level chip integration  high performance hdlc controller this application uses 30 of the available 32 serial ports. for pci bus operation, the central host processor examines the packet?s sequence and number, and manipulates the table header in local ram to perform hdlc packet formatting and de-formatting. 1.6.2 t3/e3 frame relay switch this application illustrates a connection between cx 28500 and cx28344 t3/e3 framer specifying an 6 ds3 serial ports application for an unchannelized ds3 high-end router. feature list:  supports full-rate ds3 byte streams with t3/e3 overhead and payload  supports a byte stream of 32 dwords burst size that travels over the pci bus/bridge and is directly accessible as shared memory for the host to process  uses a high-speed port priority scheme. figure 1-3 illustrates how the first payload data path ports are connected at the lower port numbers and the terminal data link (tdl) overhead data paths are connected to the low priority ports.  uses framers that can be optimally configured through an optional microprocessor. this path can be used as a inter-processor communication (ipc) path for control and performance monitoring.  supports concurrent paths of payload and overhead. (the first six ports run simultaneously at 44.2 mbps, the others run simultaneously at the tdl rate (192 kbps). note: for the detailed description of the application?s device connections, see appendix c .
introduction 28500-DSH-002-C mindspeed technologies ? 10 mindspeed proprietary and confidential figure 1-3. high-range router application cx28333 cx28333 liu liu cx28343 t3 framer cx28343 t3 framer cx28500 shared memory cpu b r i d g e pci t3/e3 t3/e3 t3/e3 t3/e3 t3/e3 t3/e3 port 0 port 1 port 2 port 3 port 4 port 5 port 6 port 7 port 8 port 9 port 10 port 11 port 12 port 13 port 14 port 15 optional local mpu mem ebus 6 ports t3/e3 overhead (tdl) see figure c-4, t3/e3 framer connection with hdlc controller (t3/e3 overhead path) 6 ports t3/e3 payload (tdl) see figure c-3, t3/e3 framer connection with hdlc controller (t3/e3 payload path) system bus see figure c-2, ds3/e3 line unit interface connection with t3/e3 framer coax (typ) 500052_004 legend: cx28333 ? ds3/e3 line interface unit cx28332 ? ds3/e3 line interface unit cx28343 ? t3 framer cx28500 ? hdlc controller
introduction 28500-DSH-002-C mindspeed technologies ? 11 mindspeed proprietary and confidential 1.6.3 128 port dsl ac cess concentrator figure 1-4 illustrates a scalable application of an internet access device (iad). cx28500, the hdlc controller, which operates at layer 2 of osi, communicates with the physical layer devices? cx28333 (t3/e3 line interface framer) and eight units of eight dsl modems. the modems are connected to cx28500?s serial port at the 16 mbps rate into a pcm highway. cx28500?s first three ports run channelized t3 and the other 16 ports run at 16 mbps so that the total port aggregated rate is 260.6 mbps. the example shows how a bank of eight modems can be configured by the serial line control serial port (csp). the csp port provides the advantage of a message buffer inter-processor control (mbipc) channel. 1.6.4 sonet/sdh mapper figure 1-5 illustrates a gigabit router line card which can perform packet pr ocessing for one oc-12/stm-4 line. feature list: figure 1-4. dslam or iad 2m 2m 2m 2m unit 15 2m 2m 2m 2m unit 0 dsl modems dsl modems x8 x8 t3 t3 t3 cx28500 cx28343 t3/e3 framer pcm csp 16m pcm pci 16m control serial port 135m port 0 port 1 port 2 port 4 port 19 port 20 t3/e3 t3/e3 t3/e3 coax (typ) ebus ebus cx28333 lui physical layer data link layer 500052_005
introduction 28500-DSH-002-C mindspeed technologies ? 12 mindspeed proprietary and confidential  ebus bus configuration to local devices  pci bus which acts as cx28500?s configuration/status interface  power solutions for hdlc processing messages (two hdlc controllers running at 66 mhz)  ipc channel processor  performance monitoring  scalable configuration up to oc-48  t3/e3 data link over the tsbus channel note: this configuration allows the power pc (ppc) to receive and transmit data link messages over these channels via its local ram (using dma and buffer table) instead of having to service individual channel fi fos with direct read/write access on each device. this effectively removes all ppc real-t ime constrains, the only remain ing real-time activity is to handle the single line interrupt from the mapper to the ppc. figure 1-5. gigabit router line card for oc-12 sonet sdh optics mapper cx29610 bam cx29503 bam cx29503 bam cx29503 bam cx29503 ppc rom ram ram pci hdlc cx28500 hdlc cx28500 ebus sibus sibus sibus sibus tsbus tsbus tsbus tsbus pci ebus = expansion bus tsbus = 84 time slot bus (x3) sibus = sonet interleaved bus pci = 66 mhz, 64-bit data bus rom = read only memory ppc = power pc bam = broadband access multiplexer (e.g. 29503) mapper = sonet/sdh mapper/framer (e.g. 29610) legend: 500052_007
introduction 28500-DSH-002-C mindspeed technologies ? 13 mindspeed proprietary and confidential 1.6.5 line card sonet/atm sar figure 1-6 illustrates the line card sonet/atm sar. feature list:  higher data aggregation  higher number of interfaces  chip cost reduced by increasing the number of interfaces serving a large number of logical channels  efficient bus occupancy when data is transferred between link layer controller and memory  fully independent serial port configuration  different types of interfaces handled simultaneously (channelized ds3 and channelized t1/e1)  32 independent serial ports  conventional mode supported by seven signals (rdat, rclk, rsync, roof, tdat, tclk, and tsync)  local bus architecture  per-channel dma buffer management, linked list data structure handled in local memory  increased pci utilization accomplished by supporting different classes of traffic with fully per-channel programmable threshold values of internal buffers. these configurable buffer thresholds allow the user to take advantage of pci bursts in transferring data between cx28500?s internal memory and shared memory. figure 1-6. line card sonet/atm sar cpu pci bridge memory (ram) at m sar cx28233 at m phy with sonet framer cx28223 pci bus cx28500 1024 channel hdlc controller with full duplex (per channel) dma quad ds3/t3 framer cx28344 triple t3/e3/sts1 liu cx28333 dual t3/e3/sts1 liu cx28332 m13 (mux/demux) + framers expansion bus interface t1/e1 t1/e1 ds3 ds3 ds3 ds3 t3 t3 t3 t3 1 28 500052_006
introduction 28500-DSH-002-C mindspeed technologies ? 14 mindspeed proprietary and confidential 1.7 feature summary the cx28500?s feature list includes the following:  a 1024-channel, full-duplex link layer controller for synchronous applications is provided.  32 full-duplex physical interfaces (i.e., ports) with independent clock rates are provided. cx28500 implements 32 serial ports that are individually programmable to operate either as conventional serial ports or tsbus serial ports. conventional serial ports? input/out data streams can be configured as channelized or unchannelized bit streams. as for tsbus serial ports, they are channelized by definition. clock rates may be as high as 52 mhz (for the first six ports) or 13 mhz (for the remaining 26 ports, see ta b l e 1 - 2 ).  general purpose hdlc (iso 3309) is supported.  hdlc/sdlc  hssi  isdn d-channel (lapd/q.921)  x.25 (lapb)  ss7  frame relay (lapf/ansi t1.618)  inter system link protocol (islp) support  lapdm support atm/smds dxi  transparent unformatted mode  point-to-point-protocol (ppp)  hyperchannels and subchannels are supported.  hyperchannel mode  isdn primary rate interface (pri)  isdn primary rate adapter (pra)  fractional t1 (ft1)  fractional e1 (fe1)  fractional nx64k  sonet/sdh/pdh paths connected via tsbus, which include: mixed vt1.5/vt2 paths, mixed tu-11/ tu-12 paths, and mixed t1/e1 paths  multiple lines muxed to 1 port, which include: digital subscriber line access multiplexer (dslam) and t1/e1 frame relay  subchanneling mode each channel can be programmed to either use a complete ds0 time slot or mask any subset of a time slot. a signal mask is defined per-channel basis that ha s an enabled bit per each time slot. the mask bit indicates whether the whole ds0 or part of it is enabled  isdn basic rate interface (bri)  isdn basic rate adapter (bra)  frame relay 56k and nx56k  compressed voice transparent channels (e.g., adpcm)  centralized signaling channel controllers, which include: link access procedure d-channel (lapd), common channel signaling (ccs), and signaling system #7 (ss7)
introduction 28500-DSH-002-C mindspeed technologies ? 15 mindspeed proprietary and confidential  unchannelized mode  digital comm/termination equipment (dce/dte) interfaces  high speed serial interface (hssi)  inter-process communication (ipc)  v-series dte/dce interfaces (v.35)  sdsl modems and access concentrators  t3/e3 frame relay  variable path primitives are supported.  path payload  sub-channeling (n 8 kbps) where n is between 1 and 7, the fr actional bits in an 8-bit time slot.  ds0 (64 kbps) n 64 kbps, allows all types of hyperchanneling, channelized, unchannelized, or path payload as long as the bandwidth does not exceed the respective port?s bandwidth limitation  higher speed ports  unchannelized t3 (44.736 mbps)  unchannelized e3 (34.368 mbps)  hssi (52 mbps)  path overhead (performance monitoring and provisioning) t1  facilities data link (fdl)  common channel signalling (ccs)  t3/e3 terminal data link (tdl)  v.51 and v.52 signalling channels  per-channel protocol selection is supported  non-fcs mode  16-bit fcs mode  32-bit fcs mode  transparent mode  configurable logical channels are supported  standard ds0  hyperchannel  subchannel  programmable time slot allocation is supported  pointer mechanism  per-channel dma buffer management is supported  32 kb per direction receive and transmit (64 kb per chip) internal fifo  configurable dma threshold per-channel basis  programmable fifo size per-channel basis  configurable number of buffer descriptors per channel  flexible buffer descriptor handling  self service mechanism
introduction 28500-DSH-002-C mindspeed technologies ? 16 mindspeed proprietary and confidential  clear to send (cts) per-channel control of data transmission  direct pci bus interface is supported  pci bus interface (rev. 2.1)  32/64-bit multiplexed address/data bus minimizes pincount  33/66 mhz operation  burst dma capability (i.e., up to 32 dwords) minimizes the bus occupancy  ebus?expansion bus interface is provided  32-bit multiplexed address/data  allows host to control other local devices  facilitates host access to any local memory  tsbus interface  variable bandwidth time slot  multiple asynchronous paths over single port  allows sonet/sdh/pdh paths connection  mixed vt1.5/vt2 paths  mixed tu-11/tu-12 paths  mixed t1/e1 paths  580-pin bga package is used  3.3 v/2.5 v supply; 5 v-tolerant inputs  jtag access is provided  low power cmos technology is used 1.8 system overview cx28500 supports 32 fully independent serial ports that can be configured to run in channelized, unchannelized, t1 or tsbus mode. for example, in the channelized mode, the first six ports can operate at 51.84 mbps (sts-1 rate) while another 22 ports can operate at 8.192 mb ps (4xe1 rate). four more ports will be unused. each sts- 1 frame transports 28xt1, 1xt3, 21xe1 or mixed t1/e1 vtg paths. the configuration is valid as long as the overall number of time slots per the whole device is 4096 time slots or less. for other restrictions see section 1.2 . alternatively, any of cx28500?s ports can interface unchannelized data streams (hdlc or unformatted). in this mode, each of the first six ports can be configured to operate up to 52 mbps and any of the remaining 26 ports up to 13 mbps. the restriction is that the overall bandwidth must not exceed 390 mbps (per direction) while operating at 66 mhz pci clock cycles or 250 mbps (per direction) while operating at 33 mhz pci clock cycles. cx28500 manages buffer memory for each of the active data channels with common table processing structures. the on-device features allow data transmission between bu ffer memory and the serial interfaces with minimum host processor intervention. this allows the host processor to concentrate on managing the higher layers of the protocol stack. figure 1-7 illustrates cx28500?s system overview.
introduction 28500-DSH-002-C mindspeed technologies ? 17 mindspeed proprietary and confidential the tsbus interface provides multiple asynchronous paths where all tsbus frames run at 51.84 mbps. the supported tsbus framer configurations that ar e mapped into and from vsps are as follows:  there are 28 pdh framers and 28 sonet/sdh framers. either of these two categories of framers can be mapped directly to the vsps for a given configuration.  when using the pdh framers, each framer can be independently configured as a ds1 framer or as an e1 framer.  the sonet/sdh category of framers has two subcategories as the name implies. when using the sonet/ sdh framers, they all have to be configured as either sonet framers (one subcategory) or as sdh framers (the other subcategory). the configurations of the sonet/sdh framers cannot have mixed subcategories. when configuring for the sonet subcategory of framers, each framer can be independently configured as a vt1.5 framer or as a vt2.0 framer. the sdh subcategory of framers is similarly configured. each sdh framer can be independently configured as a vc-11 framer or as an e1 framer. the supported tsbus frame structures are ds1s, e1s mapped via ds2, vt1.5, vt2.0, vc-11, vc-12. the following mixed mappings are also supported by selectively configuring each framer:  ds1s and e1s extracted from mixed ds2s via the pdh framers  ds1s and e1s extracted from mixed vtgs via the sonet framers  ds1s and e1s extracted from mixed vtgs via the sonet framers figure 1-7. system overview system host system memory local bus pci bridge local memory local host host interface serial interface 0 physical interface 0 physical interface 31 physical interface 30 serial interface unit (siu) serial interface 31 jtag rxdma txdma (tslp rslp) optional components local bus pci bus hdlc serial line processors pcm highway or tsbus ebus expansion bus interface (ebus) cx28500 . . . . . . 500052_008
introduction 28500-DSH-002-C mindspeed technologies ? 18 mindspeed proprietary and confidential  vc-11s and vc-12s extracted from mixed tug-2s via the sdh framers the frame structure is de signed to transport the un channelized sts-1 synchronou s payload envelope (spe). the frame structure is designed to transport the unchannelized ds3 payload. the frame structure is designed to transport 16 e1 signals that are mapped to and from e3. 1.9 block diagram figure 1-8 illustrates the cx28500 conceptual block diagram. the following is a description of the block diagram.  host interface (pci): this block provides the communication path between the host and cx28500.  expansion bus (ebus): the ebus is an extension of the host interface, which prov ides the host with access to control other devices on the local pc board.  serial interface unit (siu): this block provides the interface between 32 serial ports and the receive and transmit serial line processors block. a temporal bufferi ng space is provided by siu that is 48 bits per port, figure 1-8. cx28500 top level block diagram data stream data stream host interface (pci) rxdma and txdma serial interface unit (siu) rx line processor rslp tx line processor tslp data stream data ctrl data dwords data dwords data stream 8 8 ad[63:0] cbe[7:0]* par, par64 req64* frame* trdy* irdy* stop* devsel* idsel perr* ack64* serr* req* gnt* inta* prst_ pclk ebus jtag test access ead[31:0]* ebe_[3:0]* ale wr*(r/wr*) rd*(ds) eclk hold(br)* hlda(bg*) bgack* tdi tdo tck tms trst* 64 32 4 6 1 1 6 3 8 2 rclk0, tclk0, rsync0 (rstuff0), tsync0 (tstuff0) rdat0, roof0/cts0(tstb0), tdat0 rclk31, tclk31, rsync31 (rstuff31), tsync31(tstuff31), rdat31, roof31/cts31(tstb31), tdat31 test mode . . . . serial port 0 serial port 31 500052_001
introduction 28500-DSH-002-C mindspeed technologies ? 19 mindspeed proprietary and confidential divided as 32 bits (4 bytes) for the transmit direction and 16 bits (3 bytes) for the receive direction. siu controls the data access to the rx and tx serial line processors. given that cx28500 supports two types of serial ports, one is the conventional interface, the other tsbus interface?siu needs to operate depending on serial port type (for detailed descriptor information, see chapter 5.0 ).  transmit serial line processor (tslp): this block provides the interface between the dma and siu. the data provided by dma is processed by tslp according to the channel type (transparent/hdlc, etc.) before it is transmitted to the line.  receive serial line processor (rslp): this block prov ides the interface between the siu and dma. the data provided by siu is processed by rslp according to the channel type (transparent/hdlc, etc.) before it is transmitted to the line.  rxdma and txdma: this block provides the interface between the host memory (pci) and the transmit and receive serial line processors (tslp and rslp). the dma contains the main storage of data?a dual port ram of 32 kb per each direction, receive and transmit. th is space acts as a holding buffer for incoming (rx) and outgoing (tx) data.  jtag: this is a special test port used for serial bound ary scan on a pcb, as well as access to internal scan paths and embedded memory for test purposes. 1.10 receive data path at the siu level, all line signals are synchronized with the system pci clock, which runs either at 33 mhz or 66 mhz. the received data serial stre am is stored in siu local buffers. each cycle, the siu transfers a byte received from one of the 32 serial ports to the receive serial line processor (rslp). the order in which ports get serviced by the siu depends on their priorities. a lower numbered port has a higher priority than a higher numbered port, hence lower number ports are serviced before higher number ports. for each serial port that was served, siu translates the time slot into a channel number by using the internal map, and provides specific parameters for rslp to further process the incoming data. the rslp is a three?stage pipeline processor that performs the functions of an hdlc processor (formatting data), as well as data concatenation (i.e., to merge bytes in double words) required by rxdma. the rslp processed data is transferred to rxdma together with a related status, which indicates the status of data. the rslp received data is stored in the internal memory before it is transferred to the host. the internal memory can be configured on a per-channel basis in programmable units called the channel?s internal buffer space or channel?s fifo. the user must configure the channel fifo in quad dwords granularity by programming the start and end address of each fifo (see ta bl e 6 - 2 4 , rdma buffer allocation register , bit fields rdma_endad and rdma_startad ). when the threshold is crossed, a request to the rxdma to serve that specific channel is generated. if either an hdlc complete message (defined by an opening and closing flag) or an eom message resides in the channel fifo , then a request will be generated towards rx dma to serve the channel regardless of the threshold value. the request is queued in the rxdma service request queue, which contains all the channels pending service requests. the request is serviced when it reaches the top of the rxdma service requests queue. if the channel request gets to the top of the rxdma service request queue, then the rxdma will transfer the content of the channel fifo to the host memory. after each transaction is completed, the channel is queued at the end of rxdma service request queue until all channel data content is transferred to the host memory. 1.11 transmit data path for transmit direction, the user allocates the buffer space in quad dwords granularity for each channel by programming the start and end addresses of each channel fifo (see ta bl e 6 - 3 2 , tdma buffer allocation register , bit fields tdma_endad and tdma_startad ). transmission begins on a request generated by the
introduction 28500-DSH-002-C mindspeed technologies ? 20 mindspeed proprietary and confidential txsiu when it is ready for transmission. the request, in terms of a channel number, is passed to the tslp. if the tslp has data for the reques ted channel, then it will give that data to the txsiu. otherwise, it will generate a request, also a channel number, to th e txdma. the txdma serves the channel based on its fifo fill-state and its data availability. a channel is queued in txdma service request queue wh en the channel fifo contains less than the threshold value, or at least 32 empty dwords for the channel. when a channel request gets to the top of the txdma service requests queue, the txdma will serve this channel until the channel fifo is full. since th is may involve more than one pci transaction, the channel is inserted at the end of the txdma service request queue after each tran saction. the txdma gets data from shared memory on a per-channel basis when the internal fifo is not full. if txdma has either enough data or a complete hdlc message, then it will start transferring data to the tslp. t he tslp, in turn, does the necessary formatting, if any, and sends the data to the txsiu for transmission. the siu uses a fixed priority scheme where port a has priority over port b (when a is smaller than b). for the selected port, the siu uses a internal map conversion to identify which channel number data is transferred.
introduction 28500-DSH-002-C mindspeed technologies ? 21 mindspeed proprietary and confidential 1.12 pin configuration figure 1-9 provides a diagram of the cx28500 pin configuration, and ta b l e provides a pin description. figure 1-9. pin configuration diagram 100579_001 1 2 3 4 5 6 7 8 9 10111213141516171819202122232425262728293031323334 1 2 3 4 5 6 7 8 9 10111213141516171819202122232425262728293031323334 a b c d e f g h j k l m n p r t u v w y aa ab ac ad ae af ag ah aj ak al am an ap a b c d e f g h j k l m n p r t u v w y aa ab ac ad ae af ag ah aj ak al am an ap gnd vdd_io vdd_c signal pins as described in table 1-6 and 1-8. n these pins are not connected n n n n n n n n n n n n n n vgg
introduction 28500-DSH-002-C mindspeed technologies ? 22 mindspeed proprietary and confidential table 1-6. pin description pin number pin label a1 gnd a2 gnd a3 tdat[17] a4 tclk[17] a5 rdat[17] a6 tclk[16] a7 rdat[16] a8 tclk[15] a9 roof/cts/stb/sport [14] a10 tclk[14] a11 roof/cts/stb/sport [13] a12 rclk[13] a13 roof/cts/stb/sport [12] a14 rclk[12] a15 tdat[11] a16 rclk[11] a17 tdat[10] a18 tsync/tstuff[10] a19 rdat[10] a20 tsync/tstuff[9] a21 rdat[9] a22 tclk[8] a23 rdat[8] a24 tclk[7] a25 roof/cts/stb/sport [6] a26 tclk[6] a27 roof/cts/stb/sport [5] a28 tclk[5] a29 rsync/rstuff[5] a30 tdat[4] a31 rclk[4] a32 rdat[4] a33 gnd a34 gnd b1 gnd b2 gnd b3 gnd b4 gnd b5 rsync/rstuff[17] b6 tsync/tstuff[16] b7 gnd b8 tsync/tstuff[15] b9 rdat[15] b10 gnd b11 rdat[14] b12 tclk[13] b13 gnd b14 tclk[12] b15 roof/cts/stb/sport [11] b16 gnd b17 roof/cts/stb/sport [10] b18 tclk[10] b19 gnd b20 tclk[9] b21 roof/cts/stb/sport [8] b22 gnd b23 roof/cts/stb/sport [7] b24 rclk[7] b25 gnd b26 rclk[6] b27 tdat[5] b28 gnd b29 rdat[5] b30 tsync/tstuff[4] b31 gnd b32 gnd pin number pin label b33 gnd b34 gnd c1 gnd c2 gnd c3 gnd c4 tsync/tstuff[17] c5 roof/cts/stb/sport [17] c6 tdat[16] c7 rsync/rstuff[16] c8 tdat[15] c9 rsync/rstuff[15] c10 tsync/tstuff[14] c11 rsync/rstuff[14] c12 tsync/tstuff[13] c13 rdat[13] c14 tsync/tstuff[12] c15 rdat[12] c16 tclk[11] c17 rdat[11] c18 rclk[10] c19 roof/cts/stb/sport [9] c20 rclk[9] c21 tdat[8] c22 rclk[8] c23 tdat[7] c24 rsync/rstuff[7] c25 tdat[6] c26 rsync/rstuff[6] c27 tsync/tstuff[5] c28 rclk[5] c29 roof/cts/stb/sport [4] c30 tclk[4] c31 rsync/rstuff[4] c32 gnd pin number pin label
introduction 28500-DSH-002-C mindspeed technologies ? 23 mindspeed proprietary and confidential c33 gnd c34 gnd d1 gnd d2 gnd d3 gnd d4 gnd d5 rclk[17] d6 roof/cts/stb/sport [16] d7 rclk[16] d8 roof/cts/stb/sport [15] d9 rclk[15] d10 tdat[14] d11 rclk[14] d12 tdat[13] d13 rsync/rstuff[13] d14 tdat[12] d15 rsync/rstuff[12] d16 tsync/tstuff[11] d17 rsync/rstuff[11] d18 rsync/rstuff[10] d19 tdat[9] d20 rsync/rstuff[9] d21 tsync/tstuff[8] d22 rsync/rstuff[8] d23 tsync/tstuff[7] d24 rdat[7] d25 tsync/tstuff[6] d26 rdat[6] d27 no connect d28 no connect d29 no connect d30 no connect d31 gnd d32 roof/cts/stb/sport [3] d33 gnd pin number pin label d34 tdat[3] e1 rsync/rstuff[18] e2 rdat[18] e3 vgg e4 gnd e5 gnd e6 vdd_io e7 gnd e8 vdd_c e9 gnd e10 vdd_io e11 gnd e12 vdd_c e13 gnd e14 vdd_io e15 gnd e16 vdd_c e17 gnd e18 vdd_io e19 gnd e20 vdd_c e21 gnd e22 vdd_io e23 gnd e24 vdd_c e25 gnd e26 vdd_io e27 gnd e28 vdd_c e29 gnd e30 gnd e31 no connect e32 tsync/tstuff[3] e33 tclk[3] e34 rclk[3] f1 tdat[18] pin number pin label f2 tsync/tstuff[18] f3 tclk[18] f4 rclk[18] f5 gnd f30 vdd_io f31 no connect f32 rsync/rstuff[3] f33 rdat[3] f34 roof/cts/stb/sport [2] g1 rsync/rstuff[19] g2 gnd g3 rdat[19] g4 roof/cts/stb/sport [18] g5 vdd_c g30 gnd g31 no connect g32 tdat[2] g33 gnd g34 tsync/tstuff[2] h1 tdat[19] h2 tsync/tstuff[19] h3 tclk[19] h4 rclk[19] h5 gnd h30 vdd_c h31 no connect h32 tclk[2] h33 rclk[2] h34 rsync/rstuff[2] j1 rclk[20] j2 rsync/rstuff[20] j3 rdat[20] j4 roof/cts/stb/sport [19] j5 vdd_io j30 gnd pin number pin label
introduction 28500-DSH-002-C mindspeed technologies ? 24 mindspeed proprietary and confidential j31 rdat[2] j32 roof/cts/stb/sport [1] j33 tdat[1] j34 tsync/tstuff[1] k1 tdat[20] k2 gnd k3 tsync/tstuff[20] k4 tclk[20] k5 gnd k30 vdd_io k31 no connect k32 tclk[1] k33 gnd k34 rclk[1] l1 rclk[21] l2 rsync/rstuff[21] l3 rdat[21] l4 roof/cts/stb/sport [20] l5 vdd_c l30 gnd l31 no connect l32 rsync/rstuff[1] l33 rdat[1] l34 roof/cts/stb/sport [0] m1 roof/cts/stb/sport [21] m2 tdat[21] m3 tsync/tstuff[21] m4 tclk[21] m5 gnd m30 vdd_c m31 no connect m32 tdat[0] m33 tsync/tstuff[0] m34 tclk[0] n1 rclk[22] pin number pin label n2 gnd n3 rsync/rstuff[22] n4 rdat[22] n5 vdd_io n30 gnd n31 no connect n32 rclk[0] n33 gnd n34 rsync/rstuff[0] p1 roof/cts/stb/sport [22] p2 tdat[22] p3 tsync/tstuff[22] p4 tclk[22] p5 gnd p30 vdd_io p31 rdat[0] p32 roof/cts/stb/sport [24] p33 tdat[24] p34 tsync/tstuff[24] r1 tclk[23] r2 rclk[23] r3 rsync/rstuff[23] r4 rdat[23] r5 vdd_c r30 gnd r31 tclk[24] r32 rclk[24] r33 rsync/rstuff[24] r34 rdat[24] t1 roof/cts/stb/sport [23] t2 gnd t3 tdat[23] t4 tsync/tstuff[23] t5 gnd pin number pin label t30 vdd_c t31 roof/cts/stb/sport [25] t32 tdat[25] t33 gnd t34 tsync/tstuff[25] u1 tdo u2 tms u3 trst u4 tck u5 vdd_io u30 gnd u31 tclk[25] u32 rclk[25] u33 rsync/rstuff[25] u34 rdat[25] v1 tdi v2 tm[0] v3 tm[1] v4 tm[2] v5 gnd v30 vdd_io v31 tclk[26] v32 tsync/tstuff[26] v33 tdat[26] v34 roof/cts/stb/sport [26] w1 ebe[0] w2 gnd w3 ebe[1] w4 ebe[2] w5 vdd_c w30 gnd w31 rdat[26] w32 rsync/rstuff[26] w33 gnd w34 rclk[26] pin number pin label
introduction 28500-DSH-002-C mindspeed technologies ? 25 mindspeed proprietary and confidential y1 ebe[3] y2 bgack y3 hlda y4 hold y5 gnd y30 vdd_c y31 tclk[27] y32 tsync/tstuff[27] y33 tdat[27] y34 roof/cts/stb/sport [27] aa1 ale aa2 eclk aa3 rd aa4 wr aa5 vdd_io aa30 gnd aa31 roof/cts/stb/sport [28] aa32 rdat[27] aa33 rsync/rstuff[27] aa34 rclk[27] ab1 ead[31] ab2 gnd ab3 ead[30] ab4 ead[29] ab5 gnd ab30 vdd_io ab31 tclk[28] ab32 tsync/tstuff[28] ab33 gnd ab34 tdat[28] ac1 ead[28] ac2 ead[27] ac3 ead[26] ac4 ead[25] ac5 vdd_c pin number pin label ac30 gnd ac31 roof/cts/stb/sport [29] ac32 rdat[28] ac33 rsync/rstuff[28] ac34 rclk[28] ad1 ead[24] ad2 ead[23] ad3 ead[22] ad4 ead[21] ad5 gnd ad30 vdd_c ad31 rclk[29] ad32 tclk[29] ad33 tsync/tstuff[29] ad34 tdat[29] ae1 ead[20] ae2 gnd ae3 ead[19] ae4 ead[18] ae5 vdd_io ae30 gnd ae31 roof/cts/stb/sport [30] ae32 rdat[29] ae33 gnd ae34 rsync/rstuff[29] af1 ead[17] af2 ead[16] af3 ead[15] af4 ead[14] af5 gnd af30 vdd_io af31 rclk[30] af32 tclk[30] af33 tsync/tstuff[30] af34 tdat[30] pin number pin label ag1 ead[13] ag2 ead[12] ag3 ead[11] ag4 ead[10] ag5 vdd_c ag30 gnd ag31 tdat[31] ag32 roof/cts/stb[31] ag33 rdat[30] ag34 rsync/rstuff[30] ah1 ead[9] ah2 gnd ah3 ead[8] ah4 ead[7] ah5 gnd ah30 vdd_c ah31 rclk[31] ah32 tclk[31] ah33 gnd ah34 tsync/tstuff[31] aj1 ead[6] aj2 ead[5] aj3 ead[4] aj4 ead[3] aj5 vdd_io aj30 gnd aj31 no connect aj32 no connect aj33 rdat[31] aj34 rsync/rstuff[31] ak1 ead[2] ak2 ead[1] ak3 ead[0] ak4 vdd_io ak5 gnd ak6 gnd pin number pin label
introduction 28500-DSH-002-C mindspeed technologies ? 26 mindspeed proprietary and confidential ak7 vdd_c ak8 gnd ak9 vdd_io ak10 gnd ak11 vdd_c ak12 gnd ak13 vdd_io ak14 gnd ak15 vdd_c ak16 gnd ak17 vdd_io ak18 gnd ak19 vdd_c ak20 gnd ak21 vdd_io ak22 gnd ak23 vdd_c ak24 gnd ak25 vdd_io ak26 gnd ak27 vdd_c ak28 gnd ak29 vdd_io ak30 gnd ak31 rbs[1] ak32 rbs[2] ak33 rbs[3] ak34 rbs[4] al1 gnd al2 gnd al3 gnd al4 gnd al5 gnd al6 prst* al7 ad[31] al8 ad[28] pin number pin label al9 ad[24] al10 ad[22] al11 ad[19] al12 c/be[2]* al13 devsel al14 serr* al15 ad[14] al16 ad[10] al17 c/be[0]* al18 ad[01] al19 req64* al20 c/be[4]* al21 ad[61] al22 ad[58] al23 ad[54] al24 ad[50] al25 ad[47] al26 ad[43] al27 ad[39] al28 ad[36] al29 ad[32] al30 vdd_io al31 gnd al32 gnd al33 gnd al34 rbs[0] am1 gnd am2 gnd am3 gnd am4 gnd am5 gnd am6 pclk am7 ad[30] am8 ad[27] am9 c/be[3]* am10 ad[21] pin number pin label am11 ad[18] am12 frame* am13 stop* am14 par am15 ad[13] am16 ad[09] am17 ad[07] am18 ad[02] am19 ack64* am20 c/be[5]* am21 ad[62] am22 ad[59] am23 ad[55] am24 ad[51] am25 ad[48] am26 ad[44] am27 ad[40] am28 ad[37] am29 ad[33] am30 gnd am31 gnd am32 gnd am33 gnd am34 gnd an1 gnd an2 gnd an3 gnd an4 gnd an5 gnd an6 gnt* an7 gnd an8 ad[26] an9 idsel an10 gnd an11 ad[17] an12 irdy* pin number pin label
introduction 28500-DSH-002-C mindspeed technologies ? 27 mindspeed proprietary and confidential an13 gnd an14 c/be[1]* an15 ad[12] an16 gnd an17 ad[06] an18 ad[03] an19 gnd an20 c/be[6]* an21 ad[63] an22 gnd an23 ad[56] an24 ad[52] an25 gnd an26 ad[45] an27 ad[41] an28 gnd an29 ad[34] an30 gnd an31 gnd an32 gnd an33 gnd an34 gnd ap1 gnd ap2 gnd ap3 gnd ap4 gnd ap5 inta* ap6 req* ap7 ad[29] ap8 ad[25] ap9 ad[23] ap10 ad[20] ap11 ad[16] ap12 trdy* ap13 perr* ap14 ad[15] pin number pin label ap15 ad[11] ap16 ad[08] ap17 ad[05] ap18 ad[04] ap19 ad[00] ap20 c/be[7]* ap21 par64 ap22 ad[60] ap23 ad[57] ap24 ad[53] ap25 ad[49] ap26 ad[46] ap27 ad[42] ap28 ad[38] ap29 ad[35] ap30 vgg ap31 gnd ap32 gnd ap33 gnd ap34 gnd pin number pin label
introduction 28500-DSH-002-C mindspeed technologies ? 28 mindspeed proprietary and confidential 1.13 cx28500 hardware signals description cx28500 is packaged in a 35 mm 35 mm, 580-pin bga. the pin input/output functions are defined in ta bl e 1 - 7 . pin labels, signal names, i/o functions, and signal definitions are provided in ta bl e 1 - 8 . an active low signal is always denoted with a trailing asterisk (*). table 1-7. i/o pin types i/o definition i input. high impedance, ttl. o output. cmos. i/o input/output. ttl input/cmos output. t/s three-state. bidi rectional three-stat e input/output pin. s/t/s sustained three-state. this is an active-low, three-state sign al owned by only one driver at a time. the driver that drive s an s/t/ s signal low must drive it high for at least one clock cycle be fore allowing it to float. a pullup is required to sustain the deasserted value. o/d open drain. this output is dri ven low only, and a pullup is required to sustain the deasserted value. footnote: all outputs are cmos drive levels and can be used with cmos or ttl-logic.
introduction 28500-DSH-002-C mindspeed technologies ? 29 mindspeed proprietary and confidential table 1-8. cx28500 hardware signal definitions (1 of 7) pin label signal name i/o definition expansion bus interface eclk expansion bus clock t/s o the ebus clock can be configured to operate at the pci clock rate (i.e., 33 mhz or 66 mhz), or at half of the pci clock rate (i.e., 33/2 mhz or 66/ 2 mhz), in which case the pci clock is divided by two (see field ec_kdiv in table 6-21 ). ead[31:0] (6) expansion bus address and data t/s i/o ead[31:0] is a multiplexed address/data bus. ebe[3:0]* expansion bus byte enables s/t/s o ebe* contains byte-enabled info rmation for the ebus transaction. for details on how these signals are used and controlled by the host, see chapter 4.0 . wr* (r/wr*) write strobe s/t/s o high-to-low transiti on enables write data from cx28500 into peripheral device. rising edge defi nes write. (in motorola ? mode, r/wr* is held high throughout read and held lo w throughout write. determines meaning of ds* strobe.) rd* (ds*) read strobe s/t/s o high-to-low transition enables read data from peripheral into cx28500. held high throughout write oper ation. (in motorola mode, ds* transitions low for both read and write operations and is held low throughout the operation.) ale (as*) address latch enable s/t/s o high-to -low transition indica tes that ead[30:0] bus contains valid address. remains asserted low through the data phase of the ebus access. (in motorola mode, high-to-l ow transition indicates ebus contains a valid address. remains asserted for the entire access cycle.) hold (br*) hold request (bus request) t/s o when asserted, cx28500 requests control of the ebus. hlda (bg*) hold acknowledge (bus grant) i when asserted, cx28500 has access to the ebus. it is held asserted when there are no other masters connected to the bus, or asserted as a handshake mechanism to control ebus ar bitration. if in intel mode, then it should be pulled-down. if in motorola mode, then it should be pulled- up. bgack* bus grant acknowledge t/s o when asserted, cx28500 acknowledges to the bus arbiter that the bus grant signal was detected and a bus cycle is sustained by cx28500 until this signal is deasserted. this is used in motorola mode only.
introduction 28500-DSH-002-C mindspeed technologies ? 30 mindspeed proprietary and confidential serial interface tclk[31:0] transmit clock i if the serial port is configured in conventional mode, then tclk controls the rate at which data is transmit ted and synchronizes transitions for tdatx and sampling of tsyncx and ctsx, if ctsxis enabled. if the port is configured as a tsbus port, then tclk controls the rate at which data is transmitted and synchronizes transitions for tdatx and sampling of tstuffx and stbx (stbx only for transmit circuitry). tsync[31:0]/ tstuff[31:0] transmit synchronization/ tsbus transmit stuff i if the serial port is configured in conventional mode, then this signal is defined as tsync. tsync is sampled on the specified active edge of the corresponding tclkx clock. (see tsync_edge bit field in table 6- 36, tsiu port confi guration register .) when tsyncx signal goes from low to high then the start of transmit frame is indicated. tsyncx is ignored if the serial port is configured to operate in unchannelized mode. if the serial port is configured in t1 mode, then the corresponding data bit that latched out during the same bit time period ( but not necessarily sampled at the same clock edge) is the f-bit of the t1 frame. if the serial port is configured in channelized mode, then the corresponding data bit that latched out during the same bit time period (but not necessarily sampled at the sam e clock edge) is bit-0 of the first time slot of the n 64 frame. since cx28500?s flywheel mechanism is always used in channelized mode, no other synchronization signal is required to track the start of each subsequent frame. however, if a sync pulse, if it exists, occurs anywhere but at the frame boundaries, which are tracked by the flywheel mechanism, a cofa is generated for that port. if the port is configured to operate as tsbus port, then this signal is defined as tstuff. the tstuff valu es are to either stuff (no tdat output) or not stuf f (tdat valid). tstuff is sampled on the specified active edge of the corresponding tclkx. (see tstuff_edge bit field in table 6-36, tsiu port configuration register .) if the serial port operates in channelized tsbus mode, then tstuff assertion indicates that no data needs to be transmitted in the 8th time slot after the assertion of the tstuff. note that while operating in channelized tsbus mode, cx28500 requires the following: 1. the stuff status for each time slot to be presented at its tstuff input exactly eight time slots in advance of the actual time slot for which the stuff status is to be applied. the amount of the tstuff advance is fixed at ei ght time slots, even though the number of time slots within a frame may vary. 2. assertion of this signal anytime dur ing the time slot is required. but, for good practice, it is re commended that this signal is asserted within the first two bits of the time slot. table 1-8. cx28500 hardware signal definitions (2 of 7) pin label signal name i/o definition
introduction 28500-DSH-002-C mindspeed technologies ? 31 mindspeed proprietary and confidential serial interface (continued) tdat[31:0] transmit data t/s o serial data latched out on active edge of transmit clock, tclkx. if channel is unmapped to time slot, data bit is considered invalid and cx28500 outputs either three-state signal or l ogic 1 depending on tritx bit field value in table 6-36, tsiu port confi guration register . to avoid collision with other drivers, this signal is three- stated until the detection of the first tsync pulse, and during cofa. rclk[31:0] receive clock i if the serial port is configured in conventional mode, then rclk controls the rate at which data is transmit ted and synchronized transitions for rdatx and sampling of rsyncx and spo rt, if sport is enabled. if the port is configured as a tsbus port, th en rclk controls the rate at which data is received and synchronizes transitions for rdatx and sampling of rstuffx. rsync[31:0]/ rstuff[31:0] receive synchronization/ receive stuff i if the port operates in a conventional mode, then this signal is defined as rsync. rsync is sampled on the specified active edge of the corresponding receive clock, rclkx. (see rsync_edge bit field in table 6-28, rsiu port config uration register .) rsyncx is ignored if the serial port is configured to operate in unchannelized mode. if rsyncx signal goes from low to hi gh, then the start of a receive frame is indicated. for t1 mode, the corresponding sampled and stored data bit during the same bit-time period ( not necessarily sampled on the same clock edge) is the f-bit. for the channelized mode, the corresponding data bit sampled and stored during the same bit-time pe riod (not necessarily sampled on the same clock edge) is bit-0 of the first time slot of the n 64 frame. since cx28500?s flywheel mechanism is always used in channelized mode, no other synchronization signal is required to track the start of each subsequent frame. however, if a sync pulse, if it exists, occurs anywhere but at the frame boundaries, which are tracked by the flywheel mechanism, a cofa is generated for that port. if the port operates as a tsbus port then this signal is rstuff. the rstuff is sampled on the specified active edge of the corresponding tclkx. (see rstuff_edge bit field in table 6-28, rsiu port configuration register .) rstuff in this case assertion indicates that this time slot contains no data. rdat[31:0] receive data i serial data sampled on active edge of receive clock, rclkx. if the channel is mapped to a time slot, input bit is sampled and transferred to memory. if the channel is unmapped to time slot, data bit is considered invalid and cx28500 ignores the received sample. table 1-8. cx28500 hardware signal definitions (3 of 7) pin label signal name i/o definition
introduction 28500-DSH-002-C mindspeed technologies ? 32 mindspeed proprietary and confidential serial interface (continued) roof[31:0] (2)(3)(5) /roof/cts[31.0] (2)(3)(5) /stb/ sport[31:0] (2)(4)(5) receiver out-of-frame/ channelized clear to send/ tsbus strobe i if roofx, the signal is sampled on the specified active edge of the corresponding receive clock rclkx ( see roof_edge bit field in table 6- 28, rsiu port confi guration register ). when it is asserted high, an out-of-frame (oof) condition interrupt is indicated, if oofien bit field is set to 1 in rsiu port configuration register . while roofx is asserted, the received serial data stream is considered out-of-frame. if oofabt bit field is set to 1 in table 6-28, rsiu port configuration register , the receive process is disabled for the entire port and it remains disabled until roofx is deasserted, otherwise, the receive process is enabled. upon roofx deassertion, if oofien bit field is set to 1 in rsiu port configuration register , an interrupt frame recovery (frec) is generated. the data processing resumes for all affected channels. this signal can also operate as a genera l serial port interrupt (sport) by clearing the oofabt bit field and setting the oofien bit field in rsiu port configuration register (i.e., oofabt = 0 and oofien = 1). when the roofx signal transitions from hi gh-to-low (deasser tion), a sport interrupt is generated and data stream is not affected. if this signal is used as a general purpose interrupt, no interrupt is generated until this signal goes from high to low. if ctsx, the signal is sampled on the specified active edge of the corresponding transmit clock, tclkx. ( see cts_edge bit field in table 6-28, rsiu port config uration register .) if cts transitions from high-to-lo w (is deasserted), then the channel assigned to the time slot will send continuous id le characters after the current message has been completely transmitted. the message transmission data continues when this cts transitions from low to high again (is asserted). the response time to cts is a 32 bit-time, meaning that a new message might be transmitte d if the message starts within the next 32 bits after cts was deasserted. if tstbx, the signal is sampled twice: 1. once by the receive circuitry on the specified edge of the corresponding receive clock, rclkx. ( see rstb_edge bit field in table 6-28, rsiu port configuration register . ) 2. once by the transmit circuitr y on the specifie d edge of the corresponding transmit clock, tclkx. ( see ttstb_edge bit field in table 6-36, tsiu port confi guration register . ) if tstb transitions from low to high assertion, then it marks the first bit of time slot 0 within the tsbus frame. since there is a single tstb for both directions, receive and transmit, the number of configured time slots ( rsiu time slot pointers assignment register and tsiu time slot pointers register) and the rport_type or tport_type value (rsiu port configuration register and tsiu port configuration register ) specifying whether the serial port operates in channelized or unchannelized mode must be identically configured for both directions per serial port. un expected cx28500 behavior may be generated if this restriction is violated. table 1-8. cx28500 hardware signal definitions (4 of 7) pin label signal name i/o definition
introduction 28500-DSH-002-C mindspeed technologies ? 33 mindspeed proprietary and confidential pci interface ad[63:0] pci address and data t/s i/o ad[63:0] is a multiplexed address/ data bus. a pci transaction consists of an address phase during the first cloc k period followed by one or more data phases. ad[7:0] is the lsb. as a master, cx28500 supports both 32- and 64-bit operations. as a target, it supports only 32-bit operations. pclk pci clock i pclk provides timing for al l pci transitions. all pci signals except prst*, inta*, and intb* are synchronous to pclk and are sampled on the rising edge of pclk. cx28500 supports a pci clock up to 66 mhz. prst* pci reset i this input resets all functions on cx28500. cbe[7:0]* pci command and byte enables t/s i/o during the address phase, cbe[ 3:0]* contain command information while cbe[7:4]* are unused; during the data phases, cbe[7:0]* contain information denoting which byte lanes are valid. pci commands are defined as follows: note that the cx28500 does not accept target (slave) transactions if the cbe bits are not all 0 (zeroes). su ch transactions successfully complete on the pci bus, but are silently ignored by the cx28500 device. the cbe bits function normally during all other times. par pci parity t/s i/o the number of 1s on par, ad[31:0], and cbe[3:0]* is an even number. par always lags ad[31:0] and cb e* by one clock. during address phases, par is stable and valid one clock after the address; during the data phases it is stable and valid one clock after trdy* on reads and one clock after irdy* on writes. it rema ins valid until one clock after the completion of the data phase. par64 pci msb parity t/s i/o same as par for cbe[7:4]* and ad[63:32]. frame* pci frame s/t/s i/ o frame* is driven by the current master to indicate the beginning and duration of a bus cycle. data cycles continue as frame* stays asserted. the final data cycle is indicated by the deassertion of frame*. for a non- burst, one-data-cycle bus cycle, this pin is only asserted for the address phase. req64* request 64-bit transfer t/s i/o cx28500 asserts this si gnal when it needs to perform a 64-bit transfer. this signal is used during pci reset to inform the system that the pci is 64-bits wide. table 1-8. cx28500 hardware signal definitions (5 of 7) pin label signal name i/o definition cbe[3:0] command type oh 0000b interrupt acknowledge 1h 0001b special cycle 6h 0110b memory read 7h 0111b memory write ah 1010b configuration read bh 1011b configuration write ch 1100b memory read multiple dh 1101b dual address cycle eh 1110b memory read line fh 1111b memory write and invalidate
introduction 28500-DSH-002-C mindspeed technologies ? 34 mindspeed proprietary and confidential pci interface (continued) ack64* acknowledge 64-bit transfer s/t/s i/ o ack64* asserted indicates the selected target is ready to perform a 64- bit transaction. stop* pci stop s/t/s i/ o stop* asserted indicates the selected target is requesting the master to stop the current transaction. irdy* pci initiator ready s/t/s i/ o irdy* asserted indicates the current master?s readiness to complete the current data phase. trdy* pci target ready s/t/s i/ o trdy* asserted indicates the target?s readiness to complete the current data phase. devsel* pci device select s/t/s i/ o when asserted, devsel* indicates that the driving device has decoded its address as the target of the current cycle. idsel pci initialization device select i this input is used to select cx28500 as the target for configuration read or write cycles. serr* system error o/d o any pci device can assert serr* to indicate a pari ty error on the address cycle or parity error on the data cycle of a special cycle command or any other system error where the result will be catastrophic. cx28500 will assert serr* if it detects a pari ty error on the address cycle or encounters an abort condition while operating as a pci master. since serr* is not an s/t/s signal, r estoring it to the deasserted state is done with a weak pullup (same value as used for s/t/s). note that cx28500 does not input serr*. it is assumed that the host will reset cx28500 in the case of a catastrophic system error. perr* parity error s/t/s i/ o perr* is asserted by the agent receivi ng data when it detects a parity error on a data phase. it is asserted one clock after par is driven, which is two clocks after the ad and cbe* parity was checked. if cx28500 masters a pci write cycle and?after supplying the data during the data phase of the cycle?detects this signal being asserted by the agent receiving the data, then cx28500 generates a perr interrupt. if cx28500 masters a pci read cycle and?after receiving the data during the data phase of the cycle?calculates that a parity error has occurred, cx28500 asserts this signal and also generates the perr interrupt descriptor towards the host. inta* pci cx28500 interrupt o/d o inta* is driven by cx28500 to indicate a cx28500 layer 2 interrupt condition to the host processor. req* pci bus request t/s o cx28500 drives req* to noti fy the pci arbiter that it desires to master the bus. every master in the system has its own req*. gnt* pci bus grant i the pci bus arbiter asserts gnt* when cx28500 is free to take control of the bus, assert frame*, and execute a bus cycle. every master in the system has its own gnt*. rbs [4:0] pci read burst size t/s 0 reports the numb er of dwords cx28500 attemp ts to read during its subsequent master burst read tran saction. these lin es are driven only during address phase of the master read transaction, where a value of 00000 means one-dword and a value of 11111 means 32 dwords. table 1-8. cx28500 hardware signal definitions (6 of 7) pin label signal name i/o definition
introduction 28500-DSH-002-C mindspeed technologies ? 35 mindspeed proprietary and confidential boundary scan and test access tck jtag clock i used to clock in the tdi and tms signals and as clock out tdo signal. trst* jtag enable i an active-low input used to put the chip into a special test mode. this pin should be pulled low in normal operation. tms jtag mode select i the test signal input decoded by the tap controller to control test operations. tdo jtag data output t/s o the test signal used to transmit serial test instructions and test data. tdi jtag data input i the test signal used to r eceive serial test instructions and test data. tm[0] tm[1] tm[2] test mode i test modes, reserved for manuf acturer testing. must be tied low for normal operation. power and ground vdd_c vdd_io power ? vdd_c is power supply for internal logics. vdd_io is power supply for input and output. vgg input tolerance ? esd diode clamp supply for 5 volts tolerant input where vgg = 5 volts, otherwise vgg = vddi = vddo = 3.3 volts. gnd ground ? ground pins for internal logics, input, and output are connected to a common ground. no connection no connect no connect ? these pins have no connection. they are reserved for future revisions. footnote: (1) while operating in tsbus mode, there is no da mage expected when sampling stbx twice, since the rclkx and tclkx are the same signals for a specific port. howe ver, this may require some addi tional restrictions for the board designers when these clocks a re routed. (2) this signal is used either as receiver out-of-frame or a transm it clear to send or a tsbus stro be. (oof/frec behavior selected by oofabt = 1, cts behavior selected by ctse nb = 1, stb behavior selected by tport_ty pe or rport_type.) se e related bit fields configuration (i.e., rsiu port configuration register and tsiu port configuration register ). roof/cts/stb/sport signals are from the same pin. (3) if the serial port operates in conven tional mode, then this signal is used either as a roofx or ctsx signal. (4) if the port operates channe lized tsbus mode, then the signal is used as the tsbus strobe sign al, which indicates the beginning of the tsbus frame. (5) only one pin in the device defines all th ese functions. (6) the address line a31 must be asserted in all transactions. table 1-8. cx28500 hardware signal definitions (7 of 7) pin label signal name i/o definition
28500-DSH-002-C mindspeed technologies ? 36 mindspeed proprietary and confidential 2.0 internal architecture the cx28500 consists of the following functional blocks:  serial interface unit (siu)?tsiu and rsiu for the transmit and receive directions  serial line processing (slp)?tslp and rs lp for the transmit and receive directions  direct memory access controller (dma)  interrupt controller (intc) figure 2-1 illustrates the different signal connection between the siu and the host interf ace while the cx28500 is configured to operate in conventional or channelized tsbus mode. figure 2-1. serial interface functional block diagram host interface serial interface unit rx dma tx dma interrupt controller rslp tslp rx control rx data tx control tx data rx event rx event/error rx event/errors tx event/errors tx event/error tx event mask enabled, cofa, poll, first ts, channel number mask enabled, cofa, poll, first ts, channel number synchronization/stuff synchronization/stuff clear to send data data out-of-frame interrupt 500052_023
internal architecture 28500-DSH-002-C mindspeed technologies ? 37 mindspeed proprietary and confidential 2.1 serial interface unit (siu) the siu is the module that logically connects the 32 serial ports (line interface unit) with serial line processing by performing the serial-to-parallel conversion for the receive side, and parallel to serial for the transmit side. the siu contains two main blocks, rsiu for the receive path and tsiu for the transmit path. the rsiu main function is multiplexing 32 serial ports into one logical port for the receive serial line processing block. the tsiu main function is demultiplexing one logical port from the transmit serial line processing block to 32 serial ports. the siu main functions:  multiplexing/demultiplexing 32 serial ports to one port for the receive path, and one port to 32 serial ports for the transmit path, respectively.  performs frame integrity check while operating in channelized mode. siu verifies the length of incoming/ outgoing frames according to the configured number of time slots. in case of error a change of frame alignment (cofa) is reported (see cofa description both modes convention and tsbus mode ).  translates the time slot to logical channel number using the configured receive and transmit time slot map.  provides a poll indication per port, see rpollth or tpollth bit fields in rsiu port configuration register and tsiu port configuration register, which counts the frames of the poll interval of 1, 2, 4, 8, 16, 64, 128, or 256 frame interval.  generates the following interrupts:  rxoof, where roof signal is asserted  rxfrec, where roof signal is deasserted  rxcofa, where rsync signal is asserted in an unexpected place  rxcrec, where cofa condition is off for the receive port  txcofa, where tsync signal is asserted in an unexpected place  txcrec, where cofa condition is off for the transmit port tsiu (transmit serial interface unit) is responsible for info rming tslp (transmit serial line processor) when it is time to perform a transmit channel poll by counting a programmable (tpollth) number of frames. for the tsbus mode, one frame is defined as the stb strobe interval. tsiu is also responsible for requesting transmit data from tslp for each transmitted time slot (i.e., for each vsp). as for the rsiu, when data comes through the serial ports, it is stored in local buffers. at this stage, all line signals are synchronized to the system clock, or the pci bus rate (either 33 mhz or 66 mhz). at each cycle, the rsiu transfers a byte received from one of the 32 ports to the receive serial line processor (rslp). for the port being served, the rsiu translates the time slot to a channel number (using an internal map) and provides certain parameters that are needed by the rslp to process the incoming data. similar to the tsiu, for the tsbus mode, one frame is defined as the stb strobe interval.
internal architecture 28500-DSH-002-C mindspeed technologies ? 38 mindspeed proprietary and confidential 2.2 serial line processor (slp) the serial line processors (rslp and tslp) service the bytes in the receive and transmit path. the slp coordinates all byte-level transactions between siu and dma. the slp also interacts with the intc to notify the host of events and errors during the serial line processing. the rslp main functions are the following:  hdlc mode handling  search opening and closing flag (7eh)  abort detection (7fh)  check max/min message length  verify byte alignment check fcs  detect change of pad-fill  zero deletion  transparent mode  start to receive data from the first time slot assigned to the logical channel  bit polarity inversion  handle channel activation/deactivation  handle oof/cofa and overflow  invert incoming data  handle subchanneling  interrupts  buff, sht, chic, chabt the tslp main functions are the following:  hdlc mode handling  generate opening/closing /shared flag (7eh)  zero insertion after five consecutive 1 s bit-stuffing  generate fcs depending upon the protocol  handle cts  generate pad fill between frames  transparent mode  start to transmit data from the first time slot assigned to the logical channel  generate pad fill between messages  handle channel activation/deactivation  handle cofa and under-run  invert outgoing data  handle subchanneling  interrupts  buff, and eom
internal architecture 28500-DSH-002-C mindspeed technologies ? 39 mindspeed proprietary and confidential 2.3 direct memory access controller the direct memory access controller (rxdma and txdma) manages all of the memory operations between a correspondent?s slp and the ho st interface. dma ta kes requests from slp to either fill or flush internal fifo buffers, sets up an access to the data buffers in shared memory, and requests access to the pci bus through the host interface. 2.3.1 general feature list  handles 1024 logical channels.  supports 32- or 64-bit dma transactions for 32- or 64-bit pci bus transactions, respectively.  configurable internal buffer allocation  full control of internal buffer size and internal buffer threshold per channel  fifo flushing capability (afte r soft chip reset, channe l activation, and channel deactivation service request)  buffer descriptor handling  separate buffer descriptors per channel  last bit field set in buffer descriptor indicates the buffer descriptor table length (maximum length is 4096 buffer descriptors entries)  automatic fetch of transmit and receive head pointer table (thpt and rhpt)  automatic fetch of transmit head pointer table (thpt) and receive head pointer table (rhpt) enables the buffer descriptor tables switching without interfering normal operation (channel jump)  autonomous management of buffer descriptors  automatic fetch for next buffer descriptor  automatic buffer status descriptor update and interrupts for end of buffer (eob), ownership (onr) and end of message (eom) conditions  automatic polling of buffer descriptor  complete buffer control buffer pointer  buffer length  ownership (host/cx28500)  end of buffer interrupt mask (eobien)  poll/no poll control  self-service mechanism  zero host intervention required  support self-service for receive to transmit loopback  automatic tx abort command generation per channel configuration  inhrbd?status descriptor update/ignore  eomien?error-free end of message (eom) interrupt enable/disable  errien errored eom enable/disable  onrien?ownership error
internal architecture 28500-DSH-002-C mindspeed technologies ? 40 mindspeed proprietary and confidential interrupts  eom?end of service request without an error  eom?end of message with error (overflow, oof, cofa, fcs, align, abt lng)  onr?ownership error  eob?end of buffer 2.4 interrupt controller the interrupt controller takes receive and transmit events/errors from rsiu, rslp, rxdma and tsiu, tslp, and txdma respectively. the interrupt controller coordinates the transfer of internally queued descriptors to an interrupt queue in shared memory and coordinates notification of pending interrupts to the host.
28500-DSH-002-C mindspeed technologies ? 41 mindspeed proprietary and confidential 3.0 host interface cx28500?s host interface performs the following major functions:  transfers data between the serial interface and shared memory over the pci bus.  stores configuration state information. cx28500 does not support function 1. the access to the ebus is performed via a service request command, which provides a better utilizat ion of the pci bus for local devices located on the ebus. figure 3-1 illustrates the host interface block diagram. figure 3-1. host interface functional block diagram pci interface host interface serial interface unit pci interface device configuration registers pci configuration space clock control data interrupt tx control rx control tx data rx data interrupts 500052_019
host interface 28500-DSH-002-C mindspeed technologies ? 42 mindspeed proprietary and confidential 3.1 pci interface the host interface in cx28500 is compliant with the pci local bus specification 2.1. cx28500 provides a pci interface specific to 3.3 v and 33/66 mhz operation and supports as master a 32-bit or 64-bit bus with multiplexed address and data lines, and as a slave, a 32-bit pci bus. the host interface can act as a pci master and a pci sl ave, and contains cx28500?s pci configuration space and internal registers. when cx28500 needs to access shared memory, it masters the pci bus and completes the memory cycles without external intervention. 3.1.1 pci initialization generally, when a system initializes a module containing a pci device, the configuration manager reads the configuration space of each pci device on a pci bus. ha rdware signals select a specific pci device based on a bus number, a slot number, and a function number. if a device that is addressed (via signal lines) responds to the configuration cycle by claiming the bus, then that function?s configuration space is read out from the device during the cycle. since any pci device can be a multifunction device, every supported function?s configuration space needs to be read from the device. based on the information read, the co nfiguration manager will assign system resources to each supported function within the device. sometimes new information needs to be written into the function?s configuration space. this is ac complished with a conf iguration write cycle. cx28500 is a single function device that has device -resident memory to store the required configuration information. cx28500 supports function 0 only. 3.1.2 pci bus operations cx28500 behaves either as a pci master or a pci slave device at any time and switches between these modes as required during device operation. cx28500 supports only dword write transactions. as a pci slave, cx28500 responds to the following pci bus operations:  memory read  memory write  configuration read  configuration write  memory read multiple (treated like memory read in slave mode)  memory read line (treated like memory read in slave mode)  memory write and invalidate (treated like memory write) note: the pci local bus specification (revision 2.1, june 1, 1995) is an architectural, timing, electrical, and physical interface standard that provides a mechanism for a device to interconnect with processor and memory systems over a standard bus. note: as a pci slave, cx28500 does not support bu rsted read or write pci transactions.
host interface 28500-DSH-002-C mindspeed technologies ? 43 mindspeed proprietary and confidential as a pci master, cx28500 generates the following pci bus operations:  memory read  memory read line  memory read multiple (generated only in master mode)  memory write 3.1.3 fast back-to-back transactions fast back-to-back transactions allow agents to utilize bus bandwidth more ef fectively. cx28500 supports pci fast back-to-back transactions both as a bus target and bus master. cx28500 can also execute fast back-to-back transactions regardless of the pci co nfiguration settings (for details see bit 9 target_fbtb bit field, in ta bl e 6 - 20, global configuration descriptor ). fast back-to-back transactions ar e allowed on pci when co ntention on trdy*, devsel*, stop*, or perr* is avoided. cx28500, as a master supporting fast back-to-back transacti ons, places the burden of avoiding contention on itself. while acting as a slave, cx28500 places the burden on all the potential targets. as a master, cx28500 may remove the idle state between transactions when it can guarantee that no contention occurs. this can be accomplished when the master?s current transaction is to the same target as the previous transaction. while supporting this type of fast back-to-back transaction, cx28500 understands the address boundaries of the potential target, so that no contention occurs. the target must be able to detect a new assertion of frame* without the bus going to idle state. 3.1.3.1 operation mode during a fast back-to-back transaction, the master starts the next transaction if gnt* is still asserted. if gnt* is deasserted, the master has lost access to the bus and must relinquish the bus to the next master. the last data phase completes when frame* is deasserted, and irdy* and trdy* (or stop*) are asserted. the current master starts another transaction on the clock following the completion of the last data phase of the previous transaction. during fast back-to-back transaction, only the master and target involved need to distinguish intermediate transaction boundaries using only frame* and irdy* (there is no bus idle state). when the transaction is over, all the agents see an idle state. 3.1.3.2 example of an arb itration for fast back-to-ba ck and non-fast back-to-back transactions appendix b shows an example of an arbitration for fast back-to-back and non-fast back-to-back transactions. the transactions shown are bursts of 2, 3, 4, 5, or 6 dwords read-write transferred while the address-data is either 32- bit or 64-bit wide. 3.1.4 pci configuration space this section describes how cx28500 implements the required pci configuration register space. the intent of pci configuration space definition is to provide an appropriate set of configuration registers that satisfy the needs of current and anticipated system configuration mechanisms , without specifying those mechanisms or otherwise placing constraints on their use. these registers allow for the following:  full device relocation, in cluding interrupt binding  installation, configuration, and booting without user intervention  system address map construction by device-independent software
host interface 28500-DSH-002-C mindspeed technologies ? 44 mindspeed proprietary and confidential cx28500 only responds to type 0 configuration cycles. ty pe 1 cycles, which pass a configuration request on to another pci bus are ignored. cx28500 is a single function pci agent; therefore, it implements configuration space for function 0 only. the address phase during a cx28500 configuration cycle in dicates the function number and register number being addressed, which can be decoded by observing the status of the address lines ad[63:0]. figure 3-2 illustrates the address lines during configuration cycle. the value of the signal lines ad[10:8] selects the functi on being addressed. since cx28500 supports function 0 only, it ignores these bits. the value of the signal lines ad[7:2] during the address phase of configuration cycles selects the register of the configuration space to access. valid values are 0 through 15. accessing registers outside this range results in an all 0s value being returned on reads, and no action being taken on writes. the value of the signal lines ad[1:0] must be 00b for cx2 8500 to respond. if these bits are 0 and the idsel* signal line is asserted, then cx28500 responds to the configuration cycle. the base code register contains the class code, sub class code, and register level programming interface registers. ta b l e 3 - 1 illustrates the pci configuration space. figure 3-2. address lines during configuration cycle table 3-1. pci configuration space register number byte offset (hex) 31 24 16 8 0 0 00h device id vendor id 1 04h status command 2 08h base code revision id 3 0ch reserved header type latency timer reserved 4 10h cx28500 base address register (bar) footnote: (1) cx28500 supports function 0 only. (2) cx28500 supports registers 0 through 15, inclusively. (3) cx28500 supports type 0 configuration cycles. 63/31 8 7 2 1 0 don?t care 6-bit register number 2-bit ty p e number bit number (3) (2) (1) 500052_019a
host interface 28500-DSH-002-C mindspeed technologies ? 45 mindspeed proprietary and confidential all writable bits in the configuration space are reset to 0 by the hardware reset, prst* asserted. after reset, cx28500 is disabled and only responds to pci configuration write and pci configuration read cycles. write cycles to reserved bits and registers have no effect. read cycles to reserved bits always result in 0 being read. 3.2 pci configuration registers 3.2.1 pci master and slave cx28500 is a single function pci device that provides the necessary configuration space for a pci bus controller to query and configure cx28500?s pci interface. pci config uration space consists of a device-independent header region (64 bytes) and a device-dependent header region (192 bytes). cx28500 provides the device-independent header section only. access to the device-dependent header region results in 0s being read, and no effect on writes. three types of registers are available in cx28500: 1. read-only (ro)?return a fixed bit pattern if the register is used or a 0 if the register is unused or reserved. 2. read-resettable (rr)?can be reset to 0 by writing a 1 to the register. 3. read/write (rw)?retain the value last written to it. sixteen dword registers make up cx28500?s pci configuration space. tables 3-2 through 3-8 specify the contents of these registers. 3.2.1.1 register 0, address 00h 3.2.1.2 register 1, address 04h the status register records status information for pci bus related events. the command register provides coarse control to generate and respond to pci commands. 514h ? ? ? reserved 14 38h ? 15 3ch max latency min grant int errupt pin interrupt line table 3-2. register 0, address 00h bit field name reset value type 31:16 device id 8500h?64 channels 8501h?384 channels 8502h?676 channels 8503h?1024 channels ro 15:0 vendor id 14f1h ro table 3-1. pci configuration space register number byte offset (hex) 31 24 16 8 0
host interface 28500-DSH-002-C mindspeed technologies ? 46 mindspeed proprietary and confidential at reset, cx28500 sets the bits in this register to 0, meaning cx28500 is logically disconnected from the pci bus for all cycle types except configurati on read and configuration write cycles. table 3-3. register 1, address 04h (1 of 2) bit field name reset value type description 31 status 0 rr detected parity error. this bit is set by cx28500 whenever it detects a parity error, even if parity error response is disabled. 30 0 rr detected system error. this bit is set by cx28500 whenever it asserts serr*. 29 0 rr received master abort. this bit is set by cx28500 whenever a cx28500-initiated cycle is terminated with master-abort. 28 0 rr received target abort. cx28500 sets this bit when a cx28500-initiated cycle is terminated by a target-abort. 27 0 ro unused. 26:25 01b ro devsel timing. indicates cx28500 is a medium-speed pci device. this means the longest time it will take cx28500 to return devsel* when it is a target is 3 clocks. 24 0 rr data parity detected. cx28500 sets th is bit when three conditions are met: 1. cx28500 asserted perr* or observed perr*. 2. cx28500 was the master for that transaction. 3. parity error response bit is set. 23 1b ro fast back-to-back capable. read only. indi cates that when cx28500 is a target, it is capable of accepting fast back-to-back transacti ons when the transactions are not to the same agent. 22 0 ro unused. 21 1b ro 66 mhz capable. read only. indicates the pci interface is capable of operating at 66 mhz rate. 20:16 0 ro unused.
host interface 28500-DSH-002-C mindspeed technologies ? 47 mindspeed proprietary and confidential 15:10 command 0 ro unused. 9 0 rw fast back-to-back enable. this bit contro ls whether or not cx28500, while acting as master, can perform fast back-to-back tr ansactions to different devices. the configuration software routine sets this bit if all bus agents in the system are fast back- to-back capable. if 1, cx28500 can generate fast back-to-ba ck transactions to different agents. if 0, cx28500 can generate fast back-to- back transactions to the same agent. note that this bit would be presumably set by the system configuration routine after ensuring that all targets on the same bus ha d the fast back-to-back capable bit set. if the target is unable to provide the fast ba ck-to-back capability, the target does not implement this bit and it is automatically ret uned as zero when status register is read. 8 0 rw serr enable. if 1, disables cx28500?s serr* driver. if 0, enables cx28500?s serr* driver and allows reporting of address parity errors. 7 0 ro wait cycle control. cx28500 does not support address stepping. 6 0 rw parity error response. this bit controls cx28500?s response to parity errors. if 1, cx28500 takes normal action when a pari ty error is detected on a cycle as the target. if 0, cx28500 ignores parity errors. 5 0 ro vga palette snoop. unused. 4 0 ro memory write and invalidate. the only write cycle type cx28500 generates is memory write. 3 0 ro special cycles. unused. cx28500 ignores all special cycles. 2 0 rw bus master. if 1, cx28500 is permitted to act as bus master. if 0, cx28500 is disabled fr om generating pci accesses. 1 0 rw memory space. access control. if 1, enables cx28500 to respond to memory space access cycles. if 0, disables cx28500?s response. 0 0 ro i/o space accesses. cx28500 does not contain any i/o space registers. general note: 1. an active low signal is detect ed by a trailing asterisk (*). table 3-3. register 1, address 04h (2 of 2) bit field name reset value type description
host interface 28500-DSH-002-C mindspeed technologies ? 48 mindspeed proprietary and confidential 3.2.1.3 register 2, address 08h this location contains the class code and revision id regi sters. the class code register contains the base code, sub class, and register level programming interface fiel ds. these are used to specify the generic function of cx28500. the revision id register denotes the version of the device. 3.2.1.4 register 3, address 0ch table 3-4. register 2, address 08h bit field name reset value type description 31:24 class code 02h ro function: network controller. 23:16 sub class code 80h ro type: other. 15:8 register level programming interface 0 ro indicates there is nothing special about programming cx28500. 7:0 revision id 01h ro the revision id numbers are: 00 fo r rev a (-11p and -11r parts) and 01 for revb (-12 parts). table 3-5. register 3, address 0ch bit field name reset value type description 31:24 reserved 0 ro unused. 23:16 header type 0h ro cx28500 is a single function device wi th the standard layout of configuration register space. 15:11 latency timer 0 rw the latency timer is an 8-bit value that specifies the maximum number of pci clocks that cx28500 can keep the bus after starting the access cycle by asserting its frame*. the latency timer ensures that cx28500 has a minimum time slot for it to own the bus, but places an upper limit on how long it owns the bus. 10:8 0 ro 7:0 reserved 0 ro unused. general note: 1. an active low signal is detect ed by a trailing asterisk (*).
host interface 28500-DSH-002-C mindspeed technologies ? 49 mindspeed proprietary and confidential 3.2.1.5 register 4, address 10h 3.2.1.6 register 5?14, address 14h?38h 3.2.1.7 register 15, address 3ch table 3-6. register 4, address 10h bit field name reset value type description 31:20 cx28500 base address register 0 rw allows for 1 mb-bounded pci bus address space to be blocked off as cx28500 space. cx28500 will respond as a pci slave with devsel* to all memory cycles whose address bits 31:20 match the value of bits 31:20 of this register, and those upper address bits are non-0, and memory space is enabled in the register 1, command bit field. reads to addresses within this space that ar e not implemented read back 0; writes have no effect. 19:4 0 ro when appended to bits 31:20, these bits specify a 1 mb bound memory range. 1 mb is the only amount of address space that a cx28500 can be assigned. 3 0 ro cx28500 memory space is not prefetchable. 2:1 0 ro cx28500 can be located anywhere in 32-bit address space. 0 0 ro this base register is a memory space base register, as opposed to i/o mapped. general note: 1. an active low signal is detect ed by a trailing asterisk (*). table 3-7. register 5-14, address 14h?38h bit field name reset value type description 31:0 reserved 0 ro unused. table 3-8. register 15, address 3ch bit field name reset value type description 31:24 maximum latency 0fh ro specifies how quickly cx28500 needs to gain access to the pci bus. the value is specified in 0.25 s increments and assumes a 33 mhz clock. a value of 0fh means cx28500 needs to gain access to the pci bus every 130 pci clocks, expressed as 3.75 s in this register. 23:16 minimum grant 01h ro this value specifies, in 0.25 s increments, the minimum burst period cx28500 needs. cx28500 does not have any special min_gnt requirements. in general, the more channels cx28500 has active, the worse the bus latency and the shorter the burst cycle. 15:8 interrupt pin 01h ro defines which pci interrupt pin cx28500 uses. 01h means cx28500 uses pin inta*. 7:0 interrupt line 0 rw communicates interrupt line routing. system initialization software writes a value to this register indicating which host interrupt controller input is connected to cx28500?s inta* pin. general note: 1. an active low signal is detect ed by a trailing asterisk (*).
host interface 28500-DSH-002-C mindspeed technologies ? 50 mindspeed proprietary and confidential 3.2.2 pci reset cx28500 resets all internal functions when it detects the assertion of the prst* signal line. upon reset, the following occurs:  all pci output signals are three-stated immediately and asynchronously with respect to the pci clock input, pclk.  all ebus output signals are three-stated immediately and asynchronously with respect to the ebus clock output, eclk.  all writable/resettable internal register bits are reset to their default values.  all pci data transfers are terminated immediately.  all serial data transfers are terminated immediately.  cx28500 is disabled and responds only to pci configuration cycles. 3.2.3 pci throughput and latency considerations for reference to pci throughput and latency considerations see appendix a . 3.2.4 host interface after a hardware reset, the pci configuration space within cx 28500 needs to be configured by the host as follows:  base address register  fast back-to-back enable/disable  serr* signal driver enable/disable  parity error response enable/disable  latency timer register  interrupt line register  bus mastering enable/disable  memory space access enable/disable
28500-DSH-002-C mindspeed technologies ? 51 mindspeed proprietary and confidential 4.0 expansion bus (ebus) cx28500 provides access to a local bus interface on the cx28500 called the expansion bus (ebus), which provides a host processor to access any address in the peripheral memory space on the ebus. although ebus utilization is optional, the most notable applications for the ebus are the connections to peripheral devices (e.g., bt8370/bt8398 t1/e1 framers, cx28398 (octal ds1/e1 framers), cx28314/cx28313 (multiplexer- demultiplexer ds1 to ds3 plus framer) that are local to cx28500?s serial port. unlike other generations of conexant?s hdlc controllers (cx28478/cx28474a/cx28472a/cx28471a), cx28500 provides access to the ebus through an interface similar to a mailbox interface. this interface provides all the ebus read and write accesses to be carried over the pci bus, allowing pci bursts. this mechanism improves the pci utilization when multiple ebus acce sses are necessary for accessing th e configuration of the peripheral devices. the pci function 1 is disabled. therefore, cx28500?s ebus service requests are capable of accepting or generating burst on the pci bus. however, the ebus interface signals are not capable of performing burst. figures 4-1 and 4-2 illustrate block diagrams of the ebus interf ace with and without lo cal microprocessor (mpu). figure 4-1. ebus functional block diagram with local mpu ebus interface regenerated and inverted clock address/data clock control bus arbitration address/data local expansion bus bus arbiter mpu t1/e1 or t3/e3 framers 500052_017
expansion bus (ebus) 28500-DSH-002-C mindspeed technologies ? 52 mindspeed proprietary and confidential 4.1 ebus?operational mode 4.1.1 initialization after reset and after the pci configurat ion is completed, cx28500 provides th e host the ability to read and write peripheral devices located on the ebus (refer to ta bl e 4 - 1 ). the host service request mechanism allows the host to instruct cx28500 to perform specific ebus operatio ns. cx28500 can perform bulk service request commands. the service request acknowledge (sack) can be generated either after each service request command or at the end of each bulk service request, depending on the va lue of sackien bit field set in the service request configuration descriptor. (see ta bl e 4 - 2 .) cx28500 processes an srq by reading the hsrp register which contains the address of the first entry in the hsdt (or refer to section 7.1.2.2 ). once configured and enabled, the host can configure local devices co nnected to the ebus by issuing the ebus access service request (ebus_wr or ebus_rd). the command is a three dword memory location that contains the following dword- fields:  access control field  shared memory pointer (buffer address) representing the starting address of the buffer location where the device structure resides  ebus base address offset (the address of the first ebus transaction) figure 4-2. ebus functional block diagram without local mpu ebus interface clock address/data clock control bus arbitration address/data local expansion bus local ram peripheral devices downloadable rom 500052_018
expansion bus (ebus) 28500-DSH-002-C mindspeed technologies ? 53 mindspeed proprietary and confidential when an ebus_rd is issued, cx28500 executes a pci burs ted write of ebus transact ions and will store the data (ead[31:0]) in an internal buffer. when the ebus transaction ends, cx28500 bursts the data over the pci to the location specified by shared memory pointer (buffer address). the ebe[3:0]* drives the programmed ebus byte enabled (ebe) value set in the access control field dword. if ebe[3:0]* is different from 0000, the host must determine which bytes are valid for access. table 4-1. ebus service request descriptor dword number bit 31 bit 0 dword 0 opcode[31:27] sackien [26] reserved [25:19] fifo_burst[18] ebus byte enable [17:14] length[13:0] dword 1 shared memory pointer[31:2] (2) dword 2 ebus base address offset (3) dword 3 reserved (1) footnote: (1) all reserved bits must be written with 0?s for forward compatibility. (2) the two lsb?s must be equal to zero for dword alignment. (3) the ebus base address offset is only 31 bits wide. the msb (bit 31 ) must be set to 1 for all transactions. table 4-2. ebus service request field descriptions dword number descriptor field size (bits) value description dword 0 opcode 5 6 ebus write command (ebus_wr) 7 ebus read command (ebus_rd) sackien 1 ? enable (1) or disable (0) acknowledge via interrupt in the end of the command execution reserved 7 0 reserved bits should be written with 0s. fifo_burst 1 0 do increment ebus address (address on the target device) by one after each ebus access. this is used to access a continuous segment or block of memory on the target device that is connected to the ebus. 1 do not increment ebus address for this access. on some devices, memory accesses are carried out the wr iting/reading of one memory location. by setting fifo_burst to one, cx28500 does not in crement the ebus address after an access. hence, the address stays the same for the next ebus access. ebus byte enable (ebe) 4 ? the value driven over ebe[3:0]*. each bit controls a corresponding byte access on the ebus. for example, an ebe[3:0] value of 0001 means that host data passes to the device attached to the ebus on byte 0, the least significant byte, of the ebus while the other three bytes are inaccessible. length 14 ? number of ebus transactions. dword 1 shared memory pointer 32 ? the shared memory pointer (buffer address) is a dword?aligned address of the first buffer to or from which data needs to be transferred from or to the ebus. the two lsb?s must be equal to zero for dword alignment. dword 2 ebus base address offset 31 ? the ebus base address offset is the address for the first ebus transaction. bit 31 of this dword must be set to 1 in every transaction.
expansion bus (ebus) 28500-DSH-002-C mindspeed technologies ? 54 mindspeed proprietary and confidential if an ebus write command is enabled, cx28500 transfers?via a pci burst read?the data from the host memory into an internal buffer. the data is tr ansferred over the ebus in a series of write transactions. the ebe[3:0]* drives the programmed value ebus byte enabled (ebe) value set in the acce ss control field dwor d. if ebe[3:0]* is different from 0000, the host must insert the valid bytes into the appropriate location. 4.1.2 clock the eclk, expansion bus clock, can be configured to operate at the pci bus rate of either 33 mhz or 66 mhz, or at half of the pci bus rate of 33/2 mhz and 66/2 mhz, respectively. this option is selectable by setting the value of eclkdiv bit field in ebus configuration register. the sig nal is output on the eclk signal line. whether or not a device on the ebus requires a synchronous interface, the eclk signal is available all the time the pci clock is available (pclk). the ebus clock output can be disabled by appropriately setting the ecken bit field in ebus configuration register. if eclk is disabled, the eclk output is three-stated. after pci reset, the eclk output pin is three-stated and the ecken field in ebus configuration register is cleared. 4.1.3 interrupt unlike conexant?s other hdlc controllers (cx28478/cx28 474/cx28472), cx28500 is not connected to the eint* pin of the ebus. the ebus interrupt line should be connected to pci interrupt intb* directly, if it is needed. 4.1.4 address duration cx28500 is able to extend the duration that the address bits are valid for any given ebus address phase. this is accomplished by specifying a value between 0 and 7 in the alapse bit field in ebus configuration register. the value specifies the additional eclk periods the address bits remain asserted. that is, a value of 0 specifies the address remains asserted for one eclk period, and a value of 7 specifies the address remains asserted for 8 eclk periods. disabling the eclk signal output does not affect the delay mechanism. both pre- and post-address cycles ar e always present during the address p hase of an ebus cycle. the pre- address cycle is one eclk period long and provides cx28500 time to transition between the address phase and the following data phase. the pre- and post-cycles are not included in the address duration. 4.1.5 data duration cx28500 is able to extend the duration that the data bi ts are valid for any given ebus data phase. this is accomplished by specifying a value between 0 and 15 in the elapse bit fi eld in ebus configuration register. the value specifies the additional eclk periods the data bits remain asserted. that is, a value of 0 specifies the data remains asserted for one eclk period, and a value of 15 specifies the data remains asserted for 16 eclk periods. disabling the eclk signal output does not affect the delay mechanism. a pre-data and post-data cycle is always present during the data phase of an ebus cycle. the pre-data cycle is one eclk period long and provides cx28500 sufficient setup and hold time for the data signals. the post-data cycle is one eclk period long and provides cx28500 sufficient time to transition between the data phase and the following bus cycle termination. the pre- and post-cycles are not included in the data duration. 4.1.6 bus access interval cx28500 can be configured to wait a specified amount of time after it releases the ebus and before it requests the ebus a subsequent time. this is acco mplished by specifying a value betwe en 0 and 15 in the blapse bit field in ebus configuration register. the value specifies the additional eclk periods cx28500 waits immediately after
expansion bus (ebus) 28500-DSH-002-C mindspeed technologies ? 55 mindspeed proprietary and confidential releasing the bus. that is, a value of 0 specifies cx28500 will wait for one eclk period, and a value of 15 specifies 16 eclk periods. disabling the eclk signal output does not affect this wait mechanism. the bus grant signal (hlda/bg*) is deasserted by the bus arbiter only after the bus request signal (hold/br*) is deasserted by cx28500. as the amount of time between bus request deassertion and bus grant deassertion can vary from system to system, it is possible for a misinter pretation of the old bus grant signal as an approval to access the ebus. cx28500 provides the flexibility? through the bus access inte rval feature?to wait a specific number of eclk periods between subsequent bus requests. if the signal (hlda/bg*) is permanently asserted, then there is a minimum of 3 eclk periods between transactions. refer to ebus timing diagrams? figure 10-7, ebus write/read cycle, intel-style (intel) and figure 10-8, ebus write/read cycle, motorola-style (motorola). 4.1.7 pci to ebus interaction cx28500 provides a significant improvement in the ebus interface compared to previous conexant hdlc devices. pci utilization is dramatically improved by enab ling the ebus accesses, reads and writes, to be burst over the pci bus?when ebus is extensively used to access ebus peripheral during normal operation. 4.1.8 microprocessor interface a microprocessor can be added to handle peripheral devices that require additional processing power. the mpusel bit field in ebus configuration register specif ies the type of microprocessor interface to use for the ebus. if intel-style protocol is selected, the following signals are effective:  ale?address latch enable, asserted high by cx28500 to indicate that the address lines contain a valid address. this signal remains asserted for the duration of the access cycle.  rd*?read, strobed low by cx28500 to enable data reads out of the device and is held high during writes.  wr*?write, strobed low by cx28500 to enable data writes into the device and is held high during reads.  hold?hold request, asserted high by cx28500 when it requests the ebus from a bus arbiter.  hlda?hold acknowledge, asserted high by bus arbiter in response to hold signal assertion. remains asserted until after the hold signal is deasserted. if the ebus is connected and there are no bus arbiters on the ebus, then this signal must be asserted high at all times.  hlda is treated as an asynchronous signal. if motorola-style protocol, the following signals are effective:  as*?address strobe, driven low by cx28500 to indicate that the address lines contain a valid address. this signal remains asserted for the duration of the access cycle.  ds*?data strobe, strobed low by cx28500 to enable data reads or data writes for the addressed device.  r/wr*?read/write, held high throughout read operation and held low throughout write operation by cx28500. this signal determines the meaning (read or write) of ds*.  br*?bus request, asserted low by cx28500 when it requests the ebus from a bus arbiter.  bg*? hold acknowledge, asserted low by bus arbiter in response to br* signal assertion. remains asserted until after the br* signal is deasserted. if the ebus is connected and there are no bus arbiters on the ebus, then this signal must be asserted low at all times.  bgack*?bus grant acknowledge, asserted low by cx28500 when it detects bgack* currently deasserted. as this signal is asserted, cx28500 begins the ebus acce ss cycle. after the cycle is finished, this signal is deasserted indicating to the bus arbiter that cx28500 has released the ebus.
expansion bus (ebus) 28500-DSH-002-C mindspeed technologies ? 56 mindspeed proprietary and confidential 4.1.9 arbitration the hold and hlda (intel) or br* and bg* (motorola) signal lines are used by cx28500 to arbitrate for the ebus. for intel-style interfaces, the arbitration protocol is as follows (refer to figure 10-7, ebus write/read cycle, intel- style ) . 1. cx28500 three-states ead[31:0], ebe*[3:0]. wr*, rd*, and ale*. 2. cx28500 requires ebus access and asserts hold. 3. cx28500 checks for hlda assertion by bus arbiter. 4. if hlda is found to be deasserted, cx28500 waits for the hlda signal to become asserted before continuing the ebus operation. 5. if hlda is found to be asserted, cx28500 continues with the ebus access as it has control of the ebus. 6. cx28500 drives the address lines (ead[30:0]), ebe*[3:0], wr*, rd*, a nd ale*. the data lines (ead[31:0]) are driven one cycle later than the other aforementioned signals. 7. cx28500 completes ebus access and deasserts hold. 8. bus arbiter deasserts hlda shortly thereafter. 9. cx28500 three-states ead[31:0], ebe*[3:0]. wr*, rd*, and ale*. for motorola-style interfaces, the arbitration protocol is as follows (refer to figure 10-8, ebus write/read cycle, motorola-style ) . 1. cx28500 three-states ead[31:0], ebe*[3:0]. r/wr*, ds*, and as*. 2. cx28500 requires ebus access and asserts br*. 3. cx28500 checks for bg* assertion by bus arbiter. 4. if bg* is found to be deasserted, cx28500 waits for the bg* signal to become asserted before continuing the ebus operation. 5. if bg* is found to be asserted, cx28500 continues with the ebus access as it has control of the ebus. 6. if bgack* is not asserted cx28500 assumes control of the ebus by asserting bgack*. 7. cx28500 drives the address lines (ead[30:0]), ebe*[3:0], r/wr*, ds*, as*. the data lines (ead[31:0]) are driven one cycle later than the other aforementioned signals. 8. shortly after the ebus cycle is started, cx28500 deasserts br*. 9. bus arbiter deasserts bg* shortly thereafter. 10. cx28500 completes ebus cycle. 11. cx28500 deasserts bgack*. 12. cx28500 three-states ead[31:0], ebe*[3:0]. r/wr*, ds*, and as*. 4.1.10 connection utilizing the ebus address lines, ead[17: 0], and the byte enable lines, ebe[3:0] *, the ebus can be connected in either a multiplexed or non-multiplexed address and data mode.
expansion bus (ebus) 28500-DSH-002-C mindspeed technologies ? 57 mindspeed proprietary and confidential figures 4-3 and 4-4 illustrate two examples of non-mu ltiplexed address and data modes. figure 4-3 illustrates four separate byte-wide framer devices connected to the ebus with each byte enable line used as the chip select for separate devices, which allows a full dword data transfer over the ebus. figure 4-4 illustrates how additional address lines can be combined with each by te enable line during the address phase to support multiple framer banks with each bank containing four byte-wide framer devices. the framers configuration in shared memory is that only the least significant byte (lsb) contains the information of one frame configuration, the others are unused. figure 4-3. ebus connection, non-multiplexed address/data, 8 framers, no local mpu bt8370 data cs* bt8370 cs* bt8370 cs* bt8370 cs* ead[31:24] ead[23:16] ead[15:8] ead[7:0] ead[8:0] cx28500 ead[31:0] device 0,4 device 3,7 ebe[3:0]* as*, r/wr*, ds*, eclk control lines ebe[0]* ebe[1]* ebe[2]* ebe[3]* ead9 chip select logic dev 0,4 device 2,6 device 1,5 addr data addr data addr data addr 500052_050 general note: 1. ebex[3:0]* selects device x in each framer block. 2. ead[31:0], as* are supplied to each framer block. 3. ebex*, as* are supplied to each chip select block.
expansion bus (ebus) 28500-DSH-002-C mindspeed technologies ? 58 mindspeed proprietary and confidential in the multiplexed address and data mode, four byte-wide peripheral devices are connected to the ebus. in this mode, 8 bits of the 32-bit ebus transfer data to and from each device individually. figure 4-5 illustrates the ebus connection, multiple xed address/data, 8 framers, no local mpu. figure 4-4. ebus connection, non-multiplexed address/data, 16 framers, no local mpu note: the multiplexed address and data mode example does not allow for 4-byte data transfers. bt8370 cs* bt8370 cs* bt8370 cs* ead[31:24] ead[23:16] ead[15:8] ead[8:0] framer bank 0 framer bank 1 framer bank 2 framer bank 3 dev 0, bank 0 dev 0, bank 1 dev 0, bank 2 ead[10, 9] ebe[3:0]* ead[31:0] dev 0 8 98 98989 chip select logic cx28500 control lines control bt8370 data addr data addr data addr data addr cs* dev 0, bank 3 dev 3 dev 2 dev 1 ead[7:0] 500052_051 general note: 1. ebex[3:0]* selects device x in each framer block. 2. ead[31:0], as* are supplied to each framer block. 3. ebex*, as* are supplied to each chip select block.
expansion bus (ebus) 28500-DSH-002-C mindspeed technologies ? 59 mindspeed proprietary and confidential 4.1.10.1 multiplexing address figure 4-6 illustrates the ebus connections of four 8-bit peripheral devices. the four devices are multiplexing the address in shared memory. the framer?s configuration software has to read the whole block of framers configuration before it starts demultiplexing data per device. figure 4-5. ebus connection, multiplexed address/data, 8 framers, no local mpu figure 4-6. ebus connection, multiplexed address/data, 4 framers, no local mpu as*, r/wr*, ds*, eclk control lines cs0*,cs4* cs1*,cs5* cx28500 cs2*,cs6* cs3*,cs7* ebe[3:0]* bt8370 data addr data addr data addr data addr cs* bt8370 cs* bt8370 cs* bt8370 cs* ead[8:0] chip select ead[10:9] 500052_052 ebus cx28500 ead[31:0] addr latch bt8370 bt8370 bt8370 bt8370 be2 be1 be0 ead[0:7] ad[0:x] ead[8:15] ead[16:24] ead[25:31] a0 - a9 a0 - a9 a0 - a9 a0 - a9 500052_053
28500-DSH-002-C mindspeed technologies ? 60 mindspeed proprietary and confidential 5.0 serial interface the serial interface unit (siu) is the module that logica lly connects the 32 serial ports (line interface unit) with serial line processing by performing the serial-to-parallel conversion for the receive side, and parallel to serial for the transmit side. the siu contains two main blocks, rsiu for the receive path and tsiu for the transmit path. the rsiu main function is multiplexing 32 se rial ports into one logical port for the receive serial line processing block. the tsiu main function is demultiplexing one logical port from the transmit serial line processing block to 32 serial ports. the siu main functions:  multiplexing/demultiplexing 32 serial ports to one port for the receive path, and one port to 32 serial ports for the transmit path, respectively.  performs frame integrity check while operating in channelized mode. siu verifies the length of incoming/ outgoing frames according to the configured number of time slots. in case of error a change of frame alignment (cofa) is reported (see cofa description both modes convention and tsbus mode ).  translates the time slot to logical channel number using the configured receive and transmit time slot map.  provides a poll indication per port, see rpollth or tpollth bit fields in rsiu port configuration register and tsiu port configuration register, which counts the frames of the poll interval of 1, 2, 4, 8, 16, 64, 128, or 256 frame interval.  generates the following interrupts:  rxoof, where roof signal is asserted  rxfrec, where roof signal is deasserted  rxcofa, where rsync signal is asserted in an unexpected place  rxcrec, where cofa condition is off for the receive port  txcofa, where tsync signal is asserted in an unexpected place  txcrec, where cofa condition is off for the transmit port tsiu (transmit serial interface unit) is responsible for info rming tslp (transmit serial line processor) when it is time to perform a transmit channel poll by counting a programmable (tpollth) number of frames. for the tsbus mode, one frame is defined as the stb strobe interval. tsiu is also responsible for requesting transmit data from tslp for each transmitted time slot (i.e., for each vsp). as for the rsiu, when data comes through the serial ports, it is stored in local buffers. at this stage, all line signals are synchronized to the system clock, or the pci bus rate (either 33 mhz or 66 mhz). at each cycle, the rsiu transfers a byte received from one of the 32 ports to the receive serial line processor (rslp). for the port being served, the rsiu translates the time slot to a channel number (using an internal map) and provides certain parameters that are needed by the rslp to process the incoming data. similar to the tsiu, for the tsbus mode, one frame is defined as the stb strobe interval.
serial interface 28500-DSH-002-C mindspeed technologies ? 61 mindspeed proprietary and confidential 5.1 serial port interface definition in conventional mode a receive serial port unit (rsiu) connects to four input signals: rclk, rdat, rsync, and roof. a transmit serial port unit (tsiu) connects to three input signals and one output signal: tclk, tsync, cts, and tdat, respectively. the siu is responsible for receiving and transmitting data bytes to the transmit serial line processor (tslp) and receive serial line processor (rslp). the receive and transmit data and synchronization signals are synchronous to the receive and transmit line clocks, respectively. cx28500 can be configured to sample in and latch out data signals and sample in st atus and synchronization signals on eith er the rising or falling edges of the respective line clock, namely rclk and tclk. this conf iguration is accomplished by setting the roof_edge, rsync_edge, rdat_edge, tsync_edge, and tdat_edge bit fields as detailed in table 6-28, rsiu port configuration register and table 6-36, tsiu port configuration register . the default, after reset, is to sample in and latch out data synchron ization and status on the fallin g edges of the respective lin e clock. the port mode is configured by programming the rport_type and tport_type bit fields in rsiu port confi guration register and tsiu port configuration register , respectively. when configured to operate in conventional mode, the receive and transmit directions are not related to each other so that each direction can be programmed independently of the other. 5.1.1 frame synchronization flywheel cx28500 utilizes the tsync and rsync signals to maintain a time-base, which keeps track of the active bit in the current time slot. the mechanism is referred to as t he frame synchronization flywheel. the flywheel counts the number of bits per frame and automatically rolls over the bit count according to the programmed mode. the tsync or rsync input marks the first bit in the frame. the mode specified in the rport_type bit field in table 6-28, rsiu port configuration register and tport_type bit field in ta b l e 6 - 3 6 , tsiu port configuration register and the start and end address of time slot pointer determines the number of bits in the frame. a flywheel exists for both the transmit and the receive functions for every port. the flywheel is synchronized when cx28500 detects tsyn c = 1 or rsync = 1, for transmit or receive functions, respectively. once synchronized, the flywheel maintains synchronization without further assertion of the synchronization signal. additional sync pulses do not inte rfere with the flywheel mechanism as long as they are synchronized correctly. a time slot counter within each port is reset once in each frame and tracks the current time slot being serviced. in the receive side, synchronization starts at the beginning of frame. in the transmit side, however, synchronization starts four time slots later since there is an associated latency between when the tsiu requests the tslp for data and when the tslp supplies the tsiu with the requested data. 5.1.2 change of frame alignment (cofa) a change of frame alignment (cofa) condition is defined as a frame synchronization event detected when it was not expected, and also includes the detection of the first occurrence of frame synchronization when none was present. in unchannelized mode, there are no cofa conditions because the tsync and rsync signals are ignored in this mode. in the receive direction, when a cofa condition is detected by the serial interface, an internal cofa signal is asserted until the cofa condition is declared off. a cofa condition is declared ?off? when there was a complete frame without an unexpected sync pulse. thus, an internal cofa signal is asserted for at least two frame periods. during the frame period that the internal cofa is asserted, cx28500?s serial line processor (slp) terminates all messages that are found to be active during the cofa condition. for each receiver and transmitter channel found to be active and processing a message, the corresponding message descriptor?s owner bit is note: in unchannelized mode, cx28500 ignores the tsync and rsync signals and the frame synchronization flywheel mechanism is ignored.
serial interface 28500-DSH-002-C mindspeed technologies ? 62 mindspeed proprietary and confidential returned to the host, and a buffer status descriptor is written with the cofa error encoding. the buffer status descriptor is written if the inhrbsd bit field in the rdma channel configuration register is disabled (set to 1). cx28500 then proceeds to the next message descriptor (md) from the receive message descriptor table (rmdt). in the transmit direction, however, cx28500 cannot recover from cofa without the host?s intervention. for example, a new channel activation is required. assertion of cofa condition generates a cofa interrupt encoded in the interrupt status descriptor (isd) toward the host if this interrupt is unmasked (see table 6-28, rsiu port configuration register and ta b l e 6 - 3 6 , tsiu port configuration register , respectively rcofa_en or/and tcofa_en bit fields ). if a synchronization signal (sync) is received (low to high transition on tsync or rsync) while the internal cofa is asserted, an interrupt descriptor with the cofa interrupt encoding is generated immediately if this interrupt is not masked. when the internal cofa is deasserted, cx28500 generates an interrupt descriptor with crec event encoding if the interrupt is unmasked. the receive serial bit stream processing resumes when the cofa condition is declared off. if channels are configured in hdlc mode, then channels resume immediately if the cofa condition is declared off. while in transparent mode, channels start operating in the first time slot assigned to the logical channel. thus, after a rxcofa, no channel recovery action is required because the channel recovers automatically. for each transmitter path, the active channel (regardless of message processing) is immediately deactivated. as a recovery channel action, the host needs to reactivate the channel upon termination of the cofa condition. cofa detection is not applicable in unchann elized mode. when cofa condition occurs, the transmit output is three- stated. if operating in t1 mode, the f-bit cannot be three-stated after a cofa condition. 5.1.3 out of frame (oof )/frame recovery (frec) the receiver out-of-frame (roof) signal is asserted by the serial interface sourcing the channelized data to cx28500. this signal indicates that the interface device has lost frame synchronization. in the case of multiplexed e1 lines (2xe1, 4xe1), any gi ven port roof signal can be asserted and deasserted as the time slots are received from an out-of-frame e1 followed by an in-frame e1. roof assertion is detected by the receiver serial inte rface (rsiu). if roof is asserted high and oofien bit field in the rsiu port configuration descriptor is set, an oof interrupt is generated toward the host. for each receive hdlc message that encountered an oof condition, the corresponding message descriptor?s owner bit is returned to the host and a buffer status descriptor is written with the oof error encoding, along with eom. the eom indicates that the current message is effectively ended as a result of a receiving error. the buffer status descriptor is written to host memory only if configured to do so on a per-channel basis in the rdma channel configuration register. cx28500 then proceeds to the next message descriptor in the list of messages. as for the rsiu, it starts to search for the opening flag of the next frame. for transparent mode channels, the oof causes the data that is being transferred to the host to be replaced by an all 1s sequence. no special actions are taken in this case, and the host must rely on the oof interrupt to learn about the oof. while roof is asserted, if oofabt bit fiel d in the rsiu port configuration descriptor is set, the receive process is disabled. thus cx28500 terminates any active mess ages for all active channels operating over the port; otherwise, the receive process is enabled. notice that the oof signal is examined on a per-time slot basis. therefore, oof assertion affects only those logical channels that are mapped to time slots where oof is asserted. the remaining time slots on the same serial port are not affected by the oof assertion on a specific time slot. for roof to be deasserted, cx28500 must detect at least one frame without any oof?s. as roof is deasserted, cx28500 immediately restarts normal processing on all active channels. one to three time slots after deassertion
serial interface 28500-DSH-002-C mindspeed technologies ? 63 mindspeed proprietary and confidential of roof is detected, cx28500 generates an interrupt descriptor with the frec (frame recovery) interrupt encoding if the interrupt is not masked (oofie n = 1, rsiu port configuration descriptor). 5.1.4 general serial port interrupt the roof signal can be used as a general serial port interrupt (sport). if oofabt is zero, oofien is set, and roof signal deasserts or transitions from high to low, sport interrupt is generated and the data stream processing is not affected. when roof transitions from low to high, the sport interrupt is cleared. 5.1.5 channel clear to send (cts) cx28500 transmit path can be configured to obey a channelized clear to send (cts) external signal on a per- port basis by enabling the cts_enb bit in the tsiu port configuration register. cts is sampled on the specified active edge of tclk depending on cts_edge in ta b l e 6 - 3 6 , tsiu port configuration register . if cts is deasserted (low), the channel assigned to the time slot sends continuous idle characters after the current message has been completely transmitted. if cts is asserted (high), message transmission continues. when configured to operat e in cts mode, the channels of this sp ecific port will not start a new message transmission if the cts is a logical 0. the channel response time to react to changes in the channelized cts signal is up to 32 line clocks. 5.1.6 frame alignment cx28500 utilizes the tsync and rsync signals to maintain a timebase that keeps track of the active bit in the current time slot. the mechanism is referred to as t he frame synchronization flywheel. the flywheel counts the number of bits per frame and automatically rolls over the bit count according to the programmed mode. the tsync or rsync inputs mark the first bit in the fram e. the flywheel is synchronized when cx28500 detects tsync = 1 or rsync = 1, for transmit or receive functions, respectively. once synchronized, the flywheel maintains synchronization without further assertion of the synchronization signal. the serial data stream that cx28500 can manage consists of either packetized data or unpacketized data. cx28500 supports two types of data-stream modes: hdlc and transparent. in transparent mode, message processing for every channel begins in the first time slot marked as the first time slot in the channel?s frame structure. a user needs to configure the first time slot in the rsiu time slot configuration descriptor. in the transmission side, the us er needs to mark the last time slot where the channel appears in the frame. this is done by setting the last_ts bit in the tsiu time slot configuration descriptor. for a channel configured in hdlc mode?either transmit or receive direction, the channel waits for a synchronization signal from the internal frame synchronization flywheel before starting processing of a new message after channel activation. a frame synchronization signal must be provided once; after that, cx28500 keeps track of subsequent frame bit location with its flywheel mechanism. the frame alignment is not relevant when the port is configured in unchannelized mode, although in unchannelized mode each time slot is treated as the first time slot. by configuring more than one time slot in unchannelized mode, (i.e., using tts_endad /rts_endad and tts_startad/rts_startad mechanism to define one frame) the number of time slots between frames are considered as a virtual frame synchronization for controlling the polling interval. (see ta bl e 6 - 3 6 , tsiu port configuration register and ta b l e 6 - 2 8 , rsiu port configuration register ).
serial interface 28500-DSH-002-C mindspeed technologies ? 64 mindspeed proprietary and confidential 5.1.7 polling after channel activation, cx28500 must fetch message descriptors (md) from shared memory to start the message flow in and out of shared memory. as an md is fetched, cx28500 checks the owner bit to veri fy whether the buffer is available for cx28500. if the owner bit indicates that the host still owns the buffer, the host has not prepared the data for processing in the data buffers. if poll bit is enabled, cx28500 polls the buffer descriptor until the owner bit is switched to cx28500-owned. if the owner bit is still host-owned and no poll (np = 1) an d if tonrien/ronrien bit field is set to 1 in tdma channel configuration register or rdma channel configuration register, an (onr) interrupt is generated toward the host. if the host owns the buffer and polling is enabled, the c hannel direction is suspended from processing messages, and cx28500 periodically polls the owner bit in the buff er descriptor until the owner bit is cx28500-owned. the channel is capable of leaving this suspended state autonomously. figures 5-1 and 5-2 illustrate the details. figure 5-1. rdma state machine read message descriptor (md) poll buffer descriptor (bd) write data write buffer status descriptor (bsd) rxonr rdma suspend state read head pointer always inhrbsd = 1 while there is an eom or eob inhrbsd = 0 (allow status write) cx28500 - owned owner = 0 not eom cx28500 owns the bd not eob eom or eob poll (np = 0) host - owned (owner = 1) host - owned (owner = 1) np = 1 poll (np = 0) cx28500 owned (owner = 0) onr onriem = 1 ch_act ch_jump ch_act 500052_054
serial interface 28500-DSH-002-C mindspeed technologies ? 65 mindspeed proprietary and confidential the frequency of polling is controlled independently for each port by the rpollth or tpollth bit fields in rsiu port configuration register and tsiu port configuration register (poll throttle) bit fields in ta bl e 6 - 2 8 , rsiu port configuration register for the rx direction and ta bl e 6 - 3 6 , tsiu port configuration register for the tx direction. the rpollth or tpollth bit fields in rsiu port configuration register and tsiu port configuration register, bit field specifies how often cx28500 checks the owner bit in a host-owned buffer descriptor. the values correspond to 1, 2, 4, 8, 16, 64, 128, and 256 frame periods. if the serial port is config ured to unchannelized mode, this mechanism is still implem ented. the user programs the section 6.7.6 (for the transmit) or section 6.6.6 (for the receive) as follows: 1. program the startad to point to the single entry that is used for this port in the time slot configuration descriptor. figure 5-2. tdma state machine note: for polling to work properly and efficiently, it is mandatory that the first (receive time slot)/last (transmit ti me slot) indications be configured for each channel regardless of the operational mode (i.e., hdlc, transparent, etc.). the polling mechanism in the cx28500 uses these markings as triggering points. when configured correctly, cx28500 polls on a channel once at the selected poll throttle rate instead of polling at ever y time slot allocated to that channel, as in the case of hyperchannels . when a channel consists of only one time slot, as in a dso channel, its corresponding recei ve time slot should have the first_ts bit set. likewise, its corresponding transmit ti me slot should have the last_ts bit set. read message descriptor (md) poll buffer descriptor (bd) read data write buffer status descriptor (bsd) txonr tdma suspend state read head pointer always inhtbsd = 0 (allow status write) cx28500 - owned owner = 1 cx28500 owns the bd inhtbsd = 1 while there is an eom and eob not eom not eob eom or eob poll (np = 0) host - owned (owner = 0) poll (np = 0) cx28500 owned (owner = 1) onr if tonriem = 1 an onr interrupt is generated ch_act ch_jump ch_act host-owned (owner = 0 np=1 0 500052_055
serial interface 28500-DSH-002-C mindspeed technologies ? 66 mindspeed proprietary and confidential 2. program the endad to point at the entry startad+n where n is the size of the frame to be used for the poll mechanism; n may be zero, too. 5.2 serial port interface definition in tsbus mode a port operation mode is configured by programming the tport_type and rport_type bit fields in rsiu and tsiu port configuration registers. tport_type and rp ort_type must have the same number of time slots configured for each tsbus port, and stb sampling edges must be programmed the same for both receive and transmit directions. when configured to operate in tsbus mode, the frame synchronizing signals for both receive and transmit directions are driven by the stb signal. this leaves the rsync and tsync unused, which become rstuff and tstuff signals, respectively. additionally, both rxclk and txclk signals must be synchronized so that the sampling of stb in bo th directions is consistent. 5.2.1 tsbus frame synchronization flywheel the cx28500?s tstb signal maintains a time-base that keeps track of the active bit in the current time slot. the mechanism is referred to as the frame synchronization flywheel. the flywheel counts the number of bits per frame and automatically rolls over the bit count according to the programmed mode. the tstb input marks the first bit in the frame. a flywheel exists for both the transmit and receive directions for each port. the tsb assertion works the first bit of time slot in the tsbus frame. the flywheel is synchronized when cx28500 detects tstb = 1. once synchronized, the flywheel maintains synchronization wit hout further assertion of the synchronization signal. a time slot counter within each port is reset at the beginning of each frame and tracks the current time slot being serviced. 5.2.2 tsbus change of frame alignment (cofa) a cofa condition is defined as a frame synchronization ev ent detected when it is not expected. a cofa condition also detects if the first occurrence of frame synchronization was not present. a cofa condition can occur only if tstb is asserted in any time slot position that is not the fi rst time slot of the frame. the flywheel always counts the number of time slots allocated to a specific tsbus port (when the port is enabled). if tstb is asserted at any time other than a time coincident with cx28500?s interval flywheel rollover (the first bit of ts0), cofa is reported on both receive and transmit port directions. when a cofa condition is detected by the serial interface, an internal cofa signal is asserted until the cofa condition is declared off. a cofa condition is declared off when there is a complete frame without an unexpected tstb pulse. thus, an internal cofa signal is asserted for at least two frame periods. during the frame period when the internal cofa is asserted, cx28500?s serial line processor (siu) terminates all messages that are found to be active during the cofa condition. for each receiver and transmitter channels found to be active and processing a message, the correspondi ng message descriptor?s owner bit is returned to the host, and a buffer status descriptor is written with the cofa error encoding. the buffer status descriptor is written if the inhrbsd bit field in the rdma channel configuration register is disabled (set to 1). cx28500 then proceeds to the next message descriptor (md) from table 6-39, transmit or receive message descriptor table (tmdt) or (rmdt) content . assertion of cofa condition generates a cofa interrupt encoded in the interrupt status descriptor (isd) toward host if this interrupt is unmasked. (see table 6-28, rsiu port configuration register and table 6-36, tsiu port configuration register , respectively rcofa_en or/and tcofa_en bit fields .) if a synchronization signal (tstb) is re ceived (low to high transition on tstb) while the internal cofa is asserted, an interrupt descriptor with the cofa interrupt encoding is generated immediately if this interrupt is not masked.
serial interface 28500-DSH-002-C mindspeed technologies ? 67 mindspeed proprietary and confidential when the internal cofa is deasserted, cx28500 generates an interrupt descriptor with crec event encoding if the interrupt is unmasked. the receive serial bit stream processing resumes when the cofa condition is declared off. if channels are configured in hdlc mode, channels resume immediately wh en the cofa condition is declared off. while in transparent mode, channels start operating in the first time slot assigned to the logical channel. thus, after a rxcofa, no channel recovery action is required since the channel recovers automatically. for each transmitter path, the active channel (regardless of message processing) is immediately deactivated. as a recovery channel action, host needs to reactivate the channel upon termination of the cofa condition. cofa detection is not applicable in unchannelized mode. when a cofa condition occurs, the transmit output is three- stated. 5.2.3 tsbus out of frame (o of)/frame recovery (frec) there is no out of frame (oof) condition while operati ng in tsbus mode. the roof signal is used as a tstb input pin (for reference see figure e-1, cx28500 time slot interface pins ). 5.2.4 tsbus frame alignment the serial data stream that cx28500 can manage consists of either packetized data or unpacketized data. cx28500 supports two types of data-stream modes: hdlc and transparent. in transparent mode, message processing for every channel begi ns in the time slot marked as the first time slot in the channel?s structure. regardless of the channel protocol, the user needs to configure the first time slot for both receive and transmit directions (see rfirst_ts and tfirst-ts bit fields in table 6-26, rsiu time slot configuration descriptor and table 6-34, tsiu time slot configuration descriptor ). for a channel configur ed for hdlc mode, either transmit or re ceive direction, the channel will wait for a synchronization signal from the internal frame synchronization flywheel before starting processing new messages after channel activation. a frame synchronization signal (tstb) must be provided one time, after that, cx28500 keeps track of subsequent frame bit location within the flywheel mechanism. 5.2.5 tsbus polling the polling mechanism is the same as in the conventional mode. 5.2.6 tsbus channel clear to send while operating in tsbus mode, there is no cts signal since the related input pin is defined to be tstb (for reference see figure e-1, cx28500 time slot interface pins ). 5.2.7 tsbus interface the tsbus is a time slot interface. the digital comm unication data paths and overhead channels consist of payload data and overhead data derived from either sonet or sdh data streams, and payload and overhead data derived from either electrical ds3 or e3 data str eams. one of the overhead channels may consist of hdsl messages generated and received by the command status processor (csp). the messages are provided by the local processor that is connected to access and configure local device registers. the tsbus interface is capable of full-duplex (bidirectional) transmission of data between one device and the cx28500 device. the interface consists of two, 1-bit wide serial interfaces: a bidirectional payload tsbus and bidirectional overhead tsbus.
serial interface 28500-DSH-002-C mindspeed technologies ? 68 mindspeed proprietary and confidential a tsbus frame structure is defined as an integer multiplication of bytes. there are seven signals that define the tsbus interface. in the tsbus mode, the rx and tx are sy nchronous (i.e., the first bit of tx and rx frame is sampled on the falling edge or rising edge of rc lk/tclk on tdat/rdat). tstb defines the frame synchronization, which marks the first bit of rx/tx frame. tstu ff acts as a flow control si gnal that indicates ?stuff? (update) to be sent on the following time slot mapped to the logical channel. tstuff is sampled in the first two bits of the channel?s time slot. in the tsbus transmit direction, cx28500 requires the stuff status for each time slot to be presented at its tstuff input exactly eight time slots in advance of the actu al time slot for which the stuff status is applied. the amount of the tstuff advance is fixed at eight time slots even though the number of time slots within a frame might vary. for the receive direction, cx28500 requires the stuff status for each time slot to be presented at its rstuff input on the current time slot for which the stuff is applied. 5.2.8 payload tsbus examples of the payload tsbus operates at a data rate of 51.84 mbps. it carries the data path signals derived from either sonet, sdh, electrical ds3, or the electrical e3 signals. the data on the payload tsbus is framed and consists of 84 time slots. 5.2.8.0.1 time slot bus features payload data paths are as follows:  sonet/sdh payload  electrical ds3 to ds1?x28 ds1 672 time slots  electrical e3 to e1?x16 e1 framers 651 time slots  sts-1 to ds3/e3 to x28 ds1 (672 time slots) / x21 e1 (651 time slots)  x28 ds1?672 time slots  x21 e1?651 time slots  x16 e1?496 time slots  vt1.5?672 time slots  vt2.0?651 time slots  vt1.5 to ds1?672 time slots  vt2.0 to e1?21 time slots  tug-2 to ds1?672 time slots  tug-2 to e1?651 time slots  ds1 f-bits?1 time slot  e1 si bits?1 time slot note: f-bits not mapped with ds1 signals. note: time slot 0 not mapped.
serial interface 28500-DSH-002-C mindspeed technologies ? 69 mindspeed proprietary and confidential 5.2.9 overhead tsbus examples of the overhead tsbus operates at a data rate of 12.96 mbps. it carries pdh, or sdh overhead communication channels and it carries the data monitoring and data configuration for the device that communicates through tsbus interface with cx28500. the data on the overhead tsbus is framed and consists of 84 time slots. 5.2.9.1 overhead data channels the sources and destinations of overhead data transferred to and from the overhead tsbus are as follows: sonet  sonet/sdh section dccr?3 time slots  line cddm overhead?9 time slots  spe path f2 user data?1 time slot  spe path f3 user data?1 time slot  spe n1 tandem connection?1 time slot  dx3 ? ds3 tdl overhead?1 time slot  command status processor (csp)?100 time slots 5.2.9.2 tsbus time slots the number of time slots co nfigured for data payload or overhead are illustrated in figure 5-3 . 5.2.9.2.1 tsbus references for a detailed description of the tsbus interface, see related documents: 1. mindspeed?s cx29503 data sheet (section 2.10). figure 5-3. tsbus number of time slots into a payload or overhead frame 123456 1 2 3 4 5 6 79 80 81 82 83 84 78 . . . 1 byte per time slot payload and overhead time slot bus frame = 84 time slots time slot no. 1 is first byte of payload and overhead tsbus frame time slot no. 84 is last byte of payload and overhead tsbus frame 500052_025
28500-DSH-002-C mindspeed technologies ? 70 mindspeed proprietary and confidential 6.0 memory organization cx28500 interfaces with a system host using a set of data structures located in shared memory. cx28500 also contains a set of internal registers, which control cx28500, that the host can configure. this section describes the various shared memory data structures and the layout of individual registers that are required for the operation of cx28500. 6.1 memory architecture cx28500 supports a descriptor-based memory architecture wherein data is continually moved into and out of a table of data buffers in shared memory for each active channel. this assumes a system topology in which a host and cx28500 both have access to shared memory for data control and data flow. the data structures are defined in a way that the control structures and the data structures may or may not reside in the same physical memory and may or may not be contiguous. in other words, this data structure is a table of descriptors with pointers to data buffers. the host allocates and de-allocates the required memory space as well as the size and number of data buffers within that space. 6.1.1 register map and shared memory access during cx28500's pci initialization, the system controller allocates a dedicated 1 mb-memory range to cx28500. the memory range allocated to cx28500 must not map to any other physical or shared memory. instead, the system configuration manager allocates a logical memory address range and notifies the system or bus controllers that any access to these ranges must result in a pci access cycle. cx28500 is assigned these address ranges through the pci configuration cycle. once configured , cx28500 becomes a functional pci device on the bus. as the host accesses cx28500's allocated address ranges, t he host initiates access cycles on the pci bus. it is up to individual cx28500 devices on the bus to claim thes e access cycles. as cx28500's address ranges are accessed, cx28500 behaves as a pci slave device while da ta is being read or written by the host. cx28500 responds to all access cycles where the upper 12 bits of a pci address match the upper 12 bits of cx28500?s base address register (see ta bl e 3 - 6 , register 4, address 10h ). for cx28500, a 1 mb-memory space is as signed to the cx28500 base address register, which is written into the pci configuration space address 10h, register 4 in pci configuration registers. once a base address is assigned, a register map is used to access individual device resident registers. the 1 mb-memory range assigned to cx28500 does not restrict cx28500's pci interface from attempting to access this memory space. however, cx28500 cannot respond to an access cycle that cx28500 itself initiates as the bus master. the register map provides the byte offset from the base address register where registers reside. the register map layout is given in ta b l e 6 - 1 , pci register map . it should be noted that there are two address spaces. the first one includes registers that are directly accessed by the host through the pci, and the second includes the registers existing in shared memory that are accessed by cx28500 only through the service request mechanism. therefore, the same address offsets, or registers, may appear in both register maps memory spaces.
memory organization 28500-DSH-002-C mindspeed technologies ? 71 mindspeed proprietary and confidential the only registers that can be directly accessed by the host as slave reads or writes are the rx port alive, the tx port alive, the interrupt status descriptor, the interrupt queue pointer, the interrupt queue length, the service request length, the service request pointer, and the soft reset registers specified in cx28500?s register map. when the host writes directly into a corresponding regist er, cx28500 behaves as a pci slave while this write is performed. all other registers need to be accessed through the service request mechanism. after the pci reset, when cx28500 is ready for configuration, these registers are updated with the appropriate shared memory values through a configuration write service request. after the host has configured the shared memory image of cx28500?s registers, and cx28500 has finished its local c onfiguration (i.e., srq_len bit field in service request length is reset to zero), the host issues a service request by writing directly into the service request length register. writing to this location the actual value of the service request descriptor table length from shared memory causes cx28500 to start performing the service request descriptor table. table 6-1. pci register map register byte offset number of instances reset value access type receive port alive 00000h per port 0 read only transmit port alive 00004h per port 0 read only interrupt status descriptor (3) 00008h per chip 0 read/write interrupt queue pointer 0000ch per chip 0 read/write interrupt queue length 00010h per chip 0 read/write service request length 00014h per chip 3ff (2) read/write service request pointer 00018h per chip 0 read/write soft chip reset 00020h per chip 0 write only footnote: (1) there are two address spaces. the first address space includes registers that are directly accessed by host through the pci. the se cond address space (shown in table 6-2 ) represents the cx28500?s register map accessible by cx28500 via the serv ice request mechan ism. therefore, all the re gisters shown in this table can be directly accessed by the host. (2) during internal initialization, the service request length becomes non-0 to prevent the host from writing to this register since the host can on ly modify this register when its va lue is 0. after initialization, this register is returned to 0, allowi ng the host to modify its content. (3) the interrupt status descriptor is partially readable and pa rtially writable. the write pointer cannot be modified, but the read pointer is modifiable. any wr ite accesses to the writ e pointer are ignored by cx28500. table 6-2. indirect register map address accessible via service request mechanism (1 of 2) register address number of dword registers number of instances reset value access type rslp channel status 00000h 1024 per channel 0 read only rslp channel configuration 01000h 1024 per channel ? read/write rdma buffer allocation 02000h 1024 per channel ? write only rdma configuration 03000h 1024 per channel ? write only rsiu time slot configuration 04000h 4096 per time slot ? read/write pci configuration register 4 cx28500 base address register
memory organization 28500-DSH-002-C mindspeed technologies ? 72 mindspeed proprietary and confidential it is critically important that upon channel activation, shared memory and internal register s must be initialized, valid, and available to cx28500. cx28500 uses the information within the shared memory descriptors to transfer data between the serial interface and shared memory. cx28500 assumes the information is valid once a channel is activated. 6.2 global registers 6.2.1 service request mechanism the registers that need to be configured and checked to enable the activity of the service request mechanism are as follows:  service request length register (see ta b l e 6 - 3 )  service request pointer register (see ta b l e 6 - 4 ) rsiu time slot pointer 08000h 32 per port ? read/write rsiu port configuration 08080h 32 per port 0 read/write rslp max message length1 08100h 1 per chip ? read/write rslp max message length2 08104h 1 per chip ? read/write rslp max message length3 08108h 1 per chip ? read/write receive base address head pointer (rbahp) 0810ch 1 per chip 0 read/write transmit base address head pointer (tbahp) 08110h 1 per chip 0 read/write ebus configuration 08114h 1 per chip 0 read/write global configuration 08118h 1 per chip 0 read/write tslp channel status 10000h 1024 per channel 0 read only tslp channel configuration 11000h 1024 per channel ? read/write tdma buffer allocation 12000h 1024 per channel ? read/write tdma configuration 13000h 1024 per channel ? read/write tsiu time slot configuration 1 4000h 4096 per time slot ? read/write tsiu time slot pointer 18000h 32 per port ? read/write tsiu port configuration 18080h 32 per port 0 read/write general note: 1. these registers must be accessed through th e service request mechanism. as shown in table 6-7 , these registers? corresponding addresses are written into bits [18:0] at the indirect register map address field, wh ich is located in the device configuration descriptor. 2. for better performance and ease of implementation, it is recommended that th is service request memory block be separated into two blocks for access. service requ est block 1 starts at address 00000h and ends at address 0811ch. service request block 2 starts at address 10000h and ends at address 18100h. thi s separation is made possib le by the unused memory ga p occurring between the glob al configuration register and the tslp channel status registers. table 6-2. indirect register map address accessible via service request mechanism (2 of 2) register address number of dword registers number of instances reset value access type
memory organization 28500-DSH-002-C mindspeed technologies ? 73 mindspeed proprietary and confidential the availability of the device to the host for access is an example of information provided by querying the service request length register. after the pci reset, cx28500 sets the srq_len field in service request register to all 1s or 0x3ff, until it performs all the internal initialization. since the host cannot modify the service request length register while it is non-0, the setting of this register to all 1s by cx28500 effectively prevents the host from making additional service requests that could interfere with its internal initialization. when cx28500 is finished with the internal initialization, it clears this fi eld to 0. the cleared srq_len indicates to the host that it is ready. from this point, the host is able to directly write this field with t he actual number of service requests that cx28500 needs to perform to configure its registers. the number of srqs written by the host is stored in the srq_len field. while processing the service request commands, the srq_len field indicates how many commands are yet to be processed by cx28500 before a new command can be issued. host slave writes to this register triggers the execution of the service request list specified by the service request pointer register. the service request pointer register provides the ad dress of the service request descriptor table (see ta b l e 6 - 4 ). host needs to allocate and init ialize this table in shared memory. 6.2.1.1 service request descriptor a service request descriptor (srd) is a 4-dword location in shared memory. actually, one represents an entry in the srd table. the srd is defined as a union type in c, which allows different commands to be configured in a 4- dword space. the srd can handle three different config urations: device configuration descriptor (dcd), ebus configuration descriptor (ecd), and channel configuration descriptor (ccd). note: host slave writes to srq_len fiel d, while the previous list of service requests has not been processed (i.e., srq_len is reset) implies unpredictable behavior. table 6-3. service request length register bit field name value description 31:10 rsvd 0 reserved. 9:0 srq_len [9:0] ? service request length. after a pci reset, host reads the srq_len bit field through pci slave access. while the srq_len value equals 0x3ff, cx28500 is not ready to star t the configuration of the device. if cx28500 resets this value, the device is ready to be configured. ho st directly writes at this location the number of service request descriptors (srd) which were allocated in service request descriptor table (srdt) i.e., shared memory. the srds was previously initialized and configured in srdt. this value represents the number of service request commands queued by host (i.e., the srdt), that are waiting to be performed. real-time reads from srq_len provides the number of service request commands that are waiting to be served. do not write srq_len until after the srq_ptr, or the address of the service request descriptor table, is initialized. because cx28500 starts to process service requests whenever srq_len is non- 0 by modifying srq_len to the non-0 before a valid srq_ptr is written, cx28500 processes the invalid srq_ptr, resulting in unpredictable behaviors. table 6-4. service request pointer register bit field name value description 31:3 srq_ptr [31:3] ? service request pointer. these 29 bits are appended with 000b to form a 64-bit address quadword aligned. this address points to the first entry on the service request descriptor table allocated in shared memory. 2:0 srq_ptr [2:0] 0 to ensure quadword alignment.
memory organization 28500-DSH-002-C mindspeed technologies ? 74 mindspeed proprietary and confidential a list of service request commands is defined as a sequence of srds. the following instructions, referred to in the document as opcode, are supported:  configure a port/channel  read specific descriptors  activate or reactivate a channel  deactivate a channel  jump to new buffer descriptor table  no-operation command  perform ebus access (read or write) ta bl e 6 - 5 defines the service request descriptor opcode. a service request is issued to a sp ecific channel, or per whole device . each service request command is acknowledged by sending a service request acknowledge interrupt descriptor back to the host if the sackien bit is enabled in srd. it is possible for the host to issue mu ltiple service requests successively without expecting or receiving acknowledgments from each request if the sackien bit was not set accordingly in the srd. host can only set the sackien bit in the last srd so if a sack service request acknowledge interrupt is received, it validates the whole list of service request commands. activate, deactivate, or jump commands could take a long time before they are actually executed by cx28500. cx28500 returns the sack (if sackien bit is set) immediately after it started the command execution. therefore, the host may not assume the command was actually executed just by detecting the sack was returned. another interrupt, end of command execution (eoce), is defined for each of these three commands. the host may assume the command was actually executed only after receiving the appropriate eoce. in general, sack is only issued after each service table entry is completed. however, for activate, deactivate, and jump commands, sacks are issued after slp is completed, but before dma completes (see end of command interrupt). table 6-5. service request descriptor?opcode description (1 of 2) opcode value description nop 0h no operation. this service request performs no action other than to facilitate a host service acknowledge interrupt (sack). this would be used as a unix ping-like oper ation to detect the presence of cx28500. config_wr 1h configuration write. this is a request to copy from shared memory data into cx28500?s internal registers. this service request can be issued for either one register or for the whole cx28500 register map (up to 16 k-1 registers), depending on the value of length bit field set in service request descriptor. note that the service request descriptor used for this command is device configuration descriptor. the length bit value in this descriptor is up to 16 k. assuming that th e host configures an 16 k register structure in shared memory and the length bit field is set accordingly, cx28500 configures the entire configuration in one service request command in bursts of 32 dwords (i.e., the maximum allowed pci burst). config_rd 2h configuration read. this is a request to copy the configuration of cx28500?s in ternal registers into shared memory. the configuration located at the address specified by the cx28500 register ma p base address offset is read and copied to the address specified by the shared memory address. the number of dw ords copied is specified in the length bit field. the user needs to instruct cx28500 to perform the correct numbe r of reads so that when data is written in shared memory, no data overlapping occurs. the service request descriptor used for this command is device configuration descriptor.
memory organization 28500-DSH-002-C mindspeed technologies ? 75 mindspeed proprietary and confidential 6.2.1.2 service request descriptors each srd is 4 dwords. the srds used by cx28500 are as follows:  device configuration descriptor (dcd)  ebus configuration descriptor (ecd)  channel configuration descriptor (ccd) ch_act 3h channel activation. this is a request to activate a single channel. cx28500 assumes that the channel was already configured. if the channel is currently active, this command results in a destructive termination of the current message being processed, as well as flushing any other messages residing in the channel?s fifo. cx28500 fetches the channel?s new head pointer from shared memory (actually from the transmit head po inter table (thpt) or receive head pointer table (rhpt)), before it internally activates th e channel. the service request descriptor used for this command is channel configuration descriptor. ch_deact 4h channel deactivation. this is a request to deactivate a channel. this command r esults in a destructive termination of the current message being processed, and flushing of any other messages resi ding in the channel?s fifo. the srd used for this command is channel configuration descriptor. ch_jmp 5h channel jump. this is a request to jump to a new head pointer buffer desc riptor. if there is an active tr ansfer of a message from or to shared memory, the channel jump service request comma nd (ch_jmp) is not executed unt il an eom indication is received. when an eom indication is r eceived (or if there is no active transf er), cx28500 fetches a new head pointer buffer descriptor for this channel from shared memory ( actually from the transmit head pointer table (thpt) or receive head pointer table (rhpt)). ebus_wr 6h ebus write. this is a request to execute write transaction(s) over the ebus. data is copied from host memory to the ebus. ebus_rd 7h ebus read. this is a request to execute read transaction(s) over the ebus. data is copied from the ebus address specified in the 3rd dword of ebus configuration descriptor to the sh ared memory location specified in the 2nd dword of ebus configuration descriptor. the data length copied from one location to another location is specified by length bit field in ebus configuration descriptor. note: the eb us_rd and ebus_wr service request mechanism allow a maximum of 16 k dwords transfer to/from the ebus. the tran saction is split to bursts of 32 dwords over the pci. rsvd 8h-1fh reserved table 6-5. service request descriptor?opcode description (2 of 2) opcode value description
memory organization 28500-DSH-002-C mindspeed technologies ? 76 mindspeed proprietary and confidential 6.2.1.2.1 device configur ation descriptor (dcd) ta bl e 6 - 6 presents the structure of dcd. ta bl e 6 - 7 describes these fields. table 6-6. device configuration descriptor dword number bit 31 bit 0 dword 0 opcode[31:27] sackien[26] reserved[25:14] (1) length[13:0] dword 1 shared memory pointer [31:2] (2) dword 2 reserved [31:19] (1) indirect register map address [18:2] (2) dword 3 reserved (1) footnote: (1) all reserved bits must be wri tten to 0 for forward compatibility. (2) bits [1:0] must be equal to zero for dword alignment. table 6-7. device configuration field descriptions dword number descriptor field size (bits) value description dword 0 opcode 5 1 config_wr 2 config_rd sackien 1 0 sack interrupt disabled 1 sack interrupt enabled. an appropria te interrupt is generated after the command execution is completed. reserved 12 0 a read from this field returns al l zeros. a write to this field does nothing. length 14 ? number of dword memory commands. zero length equals 16 k, but valid maximal length is [16 k?1]. therefore, a length of 0 is invalid; do not use. dword 1 shared memory pointer 32 ? address in shared memo ry where the host service request descriptor table exists. the two lsbs must equal 0 for dword alignment. dword 2 indirect register map address 19 ? register map address to the specified re gister that needs to be configured. this address is a dword-al igned address, meaning the 2 lsb must equal to 0. bits [18:2] contain the map a ddress while bits [31:19] are reserved. general note: 1. in general, reserved fields should be written with zeros.
memory organization 28500-DSH-002-C mindspeed technologies ? 77 mindspeed proprietary and confidential 6.2.1.2.2 ebus configuration descriptor (ecd) ta bl e 6 - 8 presents the ebus configuration service request descriptor. ta bl e 6 - 9 describes the ecd fields. table 6-8. ebus configuration service request descriptor dword number bit 31 bit 0 dword 0 opcode[31:27] sackien[26] reserved [ 25:19] fifo_burst[18] ebus byte enable [17:14] length[13:0] dword 1 shared memory pointer[31:2] (1) dword 2 (3) ebus base address offset[30:0] dword 3 reserved (2) footnote: (1) bits [1:0] must equal 0 for dword alignment. (2) all reserved bits must be written to zeros for forward compatibility. (3) bit 31 must be set to 1 for all transactions. table 6-9. field descriptions of ecd dword number descriptor field size (bits) value description dword 0 opcode 5 6 ebus_wr 7ebus_rd sackien 1 0 sack interrupt disabled. 1 sack interrupt enabled. reserved 7 0 a read from this field returns al l zeros. a write to this field does nothing. fifo-burst 1 0 do increment address by 1 after each ebus access. 1 do not increment ebus address for th is access. this feat ure allows same location access (i.e., fifo read/write). ebus byte enable 4 ? determinates which byte lanes carry meaningful data in ebus transactions. the be [0] applies to byte 0 (lsb). length 14 ? number of dwords to transfer ov er ebus (up to 16 k dwords, in bursts of up to 32 dwords per burst). length = 0 is not allowed. dword 1 pointer shared memory 32 ? the address of shared memory ebus base address, where the configuration of local d evices exists. this poi nter is dword-aligned, hence bits [1:0] must equal to 0. dword 2 ebus base address offset (1) 31 ? ebus base (byte-aligned) a ddress for an ebus transaction. footnote: (1) bit 31 must be set to 1 for all transactions.
memory organization 28500-DSH-002-C mindspeed technologies ? 78 mindspeed proprietary and confidential 6.2.1.2.3 channel configur ation descriptor (ccd) ta bl e 6 - 1 0 presents the structure of ccd. ta bl e 6 - 1 1 describes the ccd fields. table 6-10. channel configuration service request descriptor dword number bit 31 bit 0 dword 0 opcode[31:27] sac kien[26] reserved[25:11] (1) direction[10] channel[9:0] dword 1 reserved (1) dword 2 reserved (1) dword 3 reserved (1) footnote: (1) all reserved bits must be written to zeros for forward compatibility. table 6-11. fields description of ccd dword number descriptor field size (bits) value description dword 0 opcode 5 0 nop 3ch_activ 4 ch_deact 5ch_jump sackien 1 0 sack interrupt disabled. 1 sack interrupt enabled. reserved ? 0 a read from this field returns al l zeros. a write to this field does nothing. direction 1 0 the command is for the receive channel. 1 the command is for the transmit channel. channel 10 ? channel number. this field is interpreted as a channel number for the ch_act, ch_deact and ch_jump command. the field is interpreted as reserved for the nop command. general note: in general, reserved fields s hould be written to with zeros.
memory organization 28500-DSH-002-C mindspeed technologies ? 79 mindspeed proprietary and confidential 6.2.2 port alive registers the receive and transmit port alive registers are read-only registers. these registers can only be accessed via direct pci read. each bit of the receive and transmit port alive register represents the device port number. refer to tables 6-12 and 6-13 for these registers. these registers operate as a gate which enables or disables the access to the port configuration register. if the corresponding bit of the receive and transmit port alive register is set, a new port configuration for the specified port is allowed. after a pci reset or software chip reset, all 32 bits of the receive and transmit port alive register are cleared (set to 0). each bit is automatically set to 1 after 8 or 16 serial clock cycle occur on that specific port. after the corresponding bit is set to 1, the host can write to the port configuration register. in addition, port alive can also be reset by writing to the port configuration register. if the host writes to a dead port, the srq completes but the register is not modified. the host cannot program a new port configuration until the corresponding bit/port is set to 1 in the port alive register depending upon the direction of receive or transmit. a proper configuration sequence for accessing the port configuration register is as follows: 1. host polls the port alive register for the specific port/direction and waits (at an interval of 8?16 line clocks) until the corresponding bit in the port alive register is set. 2. host issues a service request (srq) port configuration command and waits for a service request acknowledge (sack), or polls the sr length to determine when the table entry is completed. 3. host gets the sack. 4. host checks if a new port configuration is allowed by checking he corresponding bit in the port alive register. go to 1. table 6-12. receive port alive register bit field name value type description 31:0 rpa [31:0] 0 ro this register controls the access to the receive port configuration register. if one of 32 bits is set to 1, then the receive port configuration for that sp ecific port is allowed. table 6-13. transmit port alive register bit field name value type description 31:0 tpa [31:0] 0 ro this register controls th e access to the transmit port configuration register. if one of 32 bits is set to 1, then the transmit port configuration for that sp ecific port is allowed. note: writing to the port configurat ion register causes the correspondi ng bit from the port alive register to be cleared. this bit is automatically set to 1 after 8 or 16 serial clocks occur; therefore a new port conf iguration is allowed.
memory organization 28500-DSH-002-C mindspeed technologies ? 80 mindspeed proprietary and confidential 6.2.3 soft chip reset register any write of any value to a soft chip reset (scr) generates a soft reset for cx28500. an scr write affects cx28500 exactly as pci reset, except that the pci block is not reset. no pci configuration is performed after a scr. 6.2.4 general pci note while addressing cx28500 in slave mode, every pci access must have all four byte enables active. any pci accesses without all four bytes e nabled is treated as if all four byte enables were inactive. 6.3 interrupt level descriptors cx28500 generates interrupts for a variety of reasons. interrupts are events or errors detected by cx28500 during internal processing. interrupts are generated by cx28500 and forwarded to the host for servicing. cx28500 gathers the many events and errors (generated by all units such as rxdma and txdma, rslp and tslp, and siu) and notifies the host by asserting pci interrupts. interrupt descriptors are generated by cx28500 and forwarded to the host for servicing. individual types of interrupts can be masked from being generated by setting the appropriate interrupt mask or interrupt disable bit fields in various descriptors. the interrupt mechanism, each individual interrupt, and interrupt controlling mechanisms are discussed in this section. 6.3.1 interrupt queue descriptor cx28500 employs a single interrupt queue descriptor to communicate interrupt information to the host. this descriptor is stored within cx28500 in an internal register. the descriptor in this register stores the location and the size of an interrupt queue in allocated shared memory where the interrupt descriptors is directly pushed by cx28500 while acting as a pci bus master. cx28500 requires this information to transfer interrupt descriptors to shared memory. all the interrupts are processed by the host, in an interrupt service routine (isr). cx28500 directly writes interrupt descriptors into the shared memory interrupt queue using pci bus master mode. cx28500's pci interface must be configured to allow bus mastering. the interrupt queue descriptor (i.e., interrupt queue pointer and interrupt queue length) is initialized by the host via a direct pci write transaction. after a pci reset or software chip reset (scr), the interrupt queue pointer is the first register that needs to be initialized. a typical initialization procedure is as follows: 1. the host writes in the interrupt queue pointer register allocated by performing a direct write to the address of the interrupt queue in shared memory. 2. the host writes the interrupt queue length register by performing a direct write to this location, the value of the interrupt queue length allocated in shared memory. tables 6-14 through 6-16 list the details of the interrupt queue descriptor. note: the user can change, at any time, the length of the interrupt queue (iqlen field in the interrupt queue length register) or the pointe r value of the interrupt queue pointer (iqptr field in the interrupt queue pointer register). however, writing to these registers while the chip is operating may result in flushing th e interrupts held in the internal fifo.
memory organization 28500-DSH-002-C mindspeed technologies ? 81 mindspeed proprietary and confidential 6.3.1.1 interrupt descriptors the interrupt descriptor describes the format of data transferred into the queue. there are two different types of interrupt descriptor. the first type represents dma's block-related interrupts, and the second type represents other interrupts. both types are 64-bit fields. generically, the interrupt descriptor includes fields for the following:  identifying the source of interrupt from within the cx28500 channel causing the interrupt (0?1023) and direction (receive or transmit)  events assisting the host in synchronization channel activities  errors and unexpected conditions resulting in lost data, discontinued message processing, or prevented successful completion of a service request  number of bytes transferred to or from shared memory all the interrupts are associated with a channel or direction with the following exceptions: 1. when an oof or cofa condition is detected on a serial port, only one interrupt is generated for the port until the condition is cleared and the condition reoccurs. table 6-14. interrupt queue descriptor byte offset in cx28500 register map field name dwords 000ch interrupt queue pointer 1 0010h interrupt queue length 1 table 6-15. interrupt queue pointer bit field name value description 31:3 iqptr [31:3] ? these 29 bits are appe nded with 000b to form a 64-bit aligned address. this address points to the first entry (quadword) of the interrupt queue buffer. th e host can change this field while the chip is operating. however, this results in flushing all in terrupts residing in the internal interrupts fifo. 2:0 iqptr [2:0] 0 ensures 64-bit alignment. table 6-16. interrupt queue length bit field name value description 31:15 rsvd 0 reserved. 14:0 iqlen[14:0] ? this 15-bit number specifies the number of interrupt descriptors. the maximum size for an interrupt queue is 32,768 descriptors. this is a 0-based number. a value of 1 indicates that the queue length is 2 descriptors long, the required minimum. the host can change this field while the chip is oper ating. however, this results in flushing all interrupts residing in the internal interrupts fifo. after reset, iq len is set to 0. this has the effect of blocking all the interrupt processing by cx28500. similarly, writing a 0 to iqlen forces cx28500 to stop writing interrupts. this feature can be used to switch interrupt queues. to switch interrupt queues, first write a 0 to iqlen. next, write the base address of the new interrupt queue into iqptr in the interr upt queue pointer. finally, write the new interrupt queue length into iqlen. note(s): since cx28500 must work with 64-bit alignment, there must be an even number of entries in the buffer.
memory organization 28500-DSH-002-C mindspeed technologies ? 82 mindspeed proprietary and confidential 2. the ilost interrupt bit indicates that an interrupt has been lost internally when cx28500 generates more interrupt descriptors than can be stored in the internal interrupt queue. the latency of host processing of the interrupt queue (handling the interrupts in the irs) in shared memory may cause an ilost condition. this condition is conveyed by cx28500 overwriting the ilost bit field in the last interrupt descriptor in the internal queue prior to being transferred to shared memory. the ilost field is not specific to or associated with the interrupt descriptor being over written. only the ilost bit is overwritten, and the integrity of the original descriptor is maintained. 3. the perr interrupt bit indicates that a parity error was detected by cx28500 during a pci access cycle. this condition is conveyed by cx28500 overwriting the perr bit field in the last interrupt descriptor in the internal queue prior to being transferred out to shared memory. th e bit field is not specific to or associated with the interrupt descriptor being overwritten. on ly one bit is overwritten and the integrity of the original descriptor is maintained. the cx28500 has two types of interrupt descriptor. one is the dma interrupt descriptor, and the other is the non- dma interrupt descriptor. the following items describe the errors/events reported in the dma interrupt descriptor:  ilost (interrupt lost)  rxeob/txeob (receive or transmit end of buffer)  rxonr/txonr (receive or transmit owner bit error)  rxeom (receive end of message)  rxeoce/txeoce (receive or transmit end of comma nd, i.e., activate, deactivate or jump execution)  if eom (i.e., the message is an end of message), the other errors/events reported in the dma interrupt descriptor are as follows:  rxbuff overflow  rxcofa change of frame alignment  rxoof out of frame  rxabt abort frame  rxlng long message  rxalign byte alignment error  rxfcs frame check sequence error the following items describe the errors/events reported in the non-dma interrupt descriptor.  rxbuff/txbuff (receive and transmit buffer errors)  rxsht/txeom (receive message to o short, transmit end of buffer)  rxchabt (receive change to abort)  rxchic (receive change to idle codes)  rxcofa/txcofa (receive and transmit change of frame alignment)  rxoff (receive out of frame)  progerr (programming error, an at tempt to access an illega l address within cx28500) valid only when sack = 1, ignore prog err otherwise  rxfrec/rxsport (receive frame recovery, receive serial port interrupt)  rxcrec/txcrec (receive cofa re covery, transmit cofa recovery)
memory organization 28500-DSH-002-C mindspeed technologies ? 83 mindspeed proprietary and confidential 6.3.1.1.1 dma interrupt descriptor format the dma interrupt descriptor is 69 bits wide, and th e detailed description of its field is provided in ta bl e 6 - 1 7 . the most significant bit in the dma interrupt descriptor is always read as 0. table 6-17. dma interrupt descriptors format (1 of 2) bit field name value description 63 typ 0 interrupt descriptor type 0. 62:58 rsvd ? reserved 57:48 ch [9:0] ? the channel number causing the interrupt. 47:43 rsvd ? reserved 42 dir ? 0: direction?receive 1: direction?transmit 41:40 rsvd ? reserved 39:38 int[1:0] ? 0: rxeob/txeob, (receive or transmit end of buffer) this event is generated when current data buffer has been completely processed, and the eobien bit field is set in the associated receive/ transmit buff er descriptor. the eob interrupt reports the correct number of received transmitted bytes in blen field. 1: rxonr/txonr?generated when the next buffer descriptor is not available to cx28500 when expected, the np bit field in the buffer descriptor is set and the dma is in the middle of a message, and the ownership interrupt is enabled (bit field onr in rdma channel configuration register or tdma channel configuration register). 2: rxeom?generated when end of message occurs (even if errors were detected). if eomien (bit field in the receive buffer descriptor) is enabled, an rxeom is generated regardless the value of eobien. in other words, the eom gets higher priority than an eob event. an eom interrupt reports the correct number of received bytes in blen field. only when rxeom = 1, which means an end of messages has been reported for that particular message and the rxerr field is relevant. 3: rxeoce/txeoce?end of command execution genera ted after service request channel activation, deactivation or jump. 37:36 rsvd ? reserved
memory organization 28500-DSH-002-C mindspeed technologies ? 84 mindspeed proprietary and confidential 6.3.1.1.2 non-dma interr upt descriptor format the non-dma interrupt descriptor is 64 bits wide, and the detailed description of its field is provided in ta bl e 6 - 1 8 . the most significant bit in the non-dma interrupt descriptor is always read as 1. 35:33 rxerr/ eoce[2:0] ? when this is an rxeom interrupt then this field specifies the error type: 0: receiver error (decoded)?no error. 1: rxbuff?overflow. 2: rxcofa?change of frame alignment. 3: rxoof?out of frame. 4: rxabt?abort termination. it is generated when the received message is terminated with an abort sequence (seven consecutive 1s) instead of the specific closing flag, 7eh. 5: rxlng?long message. generated when received messag e length (after zero extraction) is greater than the selected maximum message size. the message reception is terminated and transfer to shared memory is not performed. 6: rxalign?byte alignment error. it is generate d when the message payload size (after zero extraction), is not a multiple of 8 bits. this generally occurs with an fcs error. the fcs interrupt is not generated if the align interrupt was issued. 7: rxfcs?frame check sequence error. it is generate d when received hdlc frame is terminated with a byte aligned 7eh flag but the computed fcs does not match the received fcs. when this is an rxeoce or txeoce interrupt th en this field specifies the command type that was executed: 0: activate 1: deactivate 2: jump 3?7: reserved 32:28 rsvd ? reserved 27:14 blen[13:0] ? receiver?numbe r of received bytes. transmitter?buffer length. 13:1 rsvd ? reserved 0 ilost ? 0: no interrupts have been lost. 1: interrupt lost. generated when internal interrupt queue is full and more interrupt conditions are detected. because cx28500 cannot store the newest in terrupt descriptors, it discards the new interrupts and overwrites this bit in the last interrupt in an in ternal queue prior to that interrupt being transferred out to shared memory. the integrity of the descrip tor being overwritten is maintained completely. table 6-18. non-dma interrupt descriptors format (1 of 3) bit field name value description 63 typ 1 interrupt descriptor type 1. 62:58 rsvd ? reserved. 57:48 ch [9:0] ? the channel number causing the interrupt. 47:43 rsvd ? reserved. 42 chdir ? 0: receive direction. 1: transmit direction. table 6-17. dma interrupt descriptors format (2 of 2) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 85 mindspeed proprietary and confidential 41 rxbuff/ txbuff ? receive or transmit buffer errors the data is lost. cx28500 has no place to read or write data internally. if reported as txbuff, the internal buffer underruns. if reported as rxbu ff, the internal buffer overflows. 40:38 rsvd ? reserved. 37 rxsht/ txeom ? rxsht?receive direction messag e too short or other error causes a truncated message. the error is generated when the received message leng th (after zero extractio n in hdlc mode) is less than or equal to the number of bits in fcs field. the message data is not transferred to shared memory. txeom?transmit direction end of message. 36:34 rsvd ? reserved. 33 rxchabt/ txrsvd ? rxchabt?receive direction change to abort code. the event is generated when a received pad fill code changes from 7eh to 7fh (15 consecutive 1s are detected). transmit: reserved 32:30 rsvd ? reserved. 29 rxchic/ txrsvd ? rxchic?receive direction change to idle code ( rxchic) . the event is generated when a received pad fill code changes from 7fh to 7eh, or upon the detection of the first flag after channel activation. transmit: reserved. 28:25 rsvd ? reserved. 24:20 prt [4:0] ? the port number causing the interrupt. 19:18 rsvd ? reserved. 17 prtdir ? 0: receive direction of port causing the interrupt. 1: transmit direction of port causing the interrupt. 16 rxcofa/ txcofa ? receive and transmit change of frame alignment. 15 rxoof/ txrsvd ? rxoof?receive direction out of frame. generated when serial port is configured in channe lized mode and receiver-o ut-of-frame (roof) input signal assertion is detected. transmit: reserved. 14 rxfrec/ rxsport/ txrsvd ? rxfrec?receive direction. when roof signal deasserts, frame recovery (frec) in terrupt is generated. the serial port transitions from out-of-frame (oof) back to in-frame. rxsport?receive direction. when roof signal is used as a general serial port interrupt line (sport). if oofabt=0 and oofien=1 bit fields in rsiu port configuration register and roff transitions from high-to-low, the sport interrupt is generated. the data stream processing is not affected. transmit?reserved. 13 crec ? cofa recovery?generated when the internal co fa signal deasserts. the serial port transitions from cofa back to in-frame. 12:4 rsvd ? reserved. 3 progerr ? reports a programming error: an attempt was ma de to perform a srq access to an illegal address within cx28500. an illegal address is any address which is not defined in table 6-2 . reports status of sack, only valid when sack = 1. table 6-18. non-dma interrupt descriptors format (2 of 3) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 86 mindspeed proprietary and confidential 6.3.1.2 interrupt stat us descriptor register the interrupt status descriptor is located in a fixed position in cx28500?s internal register. cx28500 updates this descriptor after each transfer of interrupt descriptors from its internal queue to the interrupt queue in shared memory. the host is required to read this descriptor from cx28500?s registers before it processes any interrupts. the contents of the interrupt status descriptor are reset on hardware reset or soft chip reset or whenever any field in the interrupt queue descriptor is modified. ta bl e 6 - 1 9 lists the details of the interrupt status descriptor. 2 sack ? dma service request acknowledge. generated to conclude successfully a service request command of host service. 1 perr ? 0: no pci parity errors have been detected. 1: pci bus parity error. generated when cx28500 dete cts a parity error on data being transferred into/ from cx28500, either from another pci agent that writes into cx28500 registers or from cx28500 that reads data from shared memory. this error is specific to the data phase of a pci transfer while cx28500 is receiving data. pci system error signal, serr*, is ignored by cx28500. to mask the perr interrupt? in cx28500's pci configuration space, function 0, register 1?parity error response field must be set to 0. 0 ilost ? 0: no interrupts have been lost. 1: interrupt lost. generated when cx28500?s (interna l) interrupt queue is full and more interrupt conditions are detected. as cx28500 has no way to stor e the newest interrupt descriptors, it discards the new interrupts and overwrites this bit in the last interr upt in an internal queue prior to that interrupt being transferred out to shared memory. the integrity of the descriptor being overwritten is maintained completely. note: this internal register is directly accessed by the host. table 6-19. interrupt status descriptor bit field name host access value description 31 mstrabt r ? when cx28500 encounters a pci abort while operating as a pci master, it does not attempt to recover from this error. in this case cx28500 asserts the serr* signal, and the mstrabt bit and waits for the host to reset (i.e., pci reset or soft reset). this bit is asserted when the target does not assert devsel within a specific pclk cycles or when the target terminates a transaction in which cx28500 is the master, with an abort (i.e., asser tion of stop# with a deassertion of devsel) sequence. table 6-18. non-dma interrupt descriptors format (3 of 3) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 87 mindspeed proprietary and confidential 6.3.1.3 interrupt handling 6.3.1.3.1 initialization interrupt management resources are automatically reset upon the following:  hardware reset  soft reset  write to interrupt queue pointer by a direct pci write  write to interrupt queue length by a direct pci write cx28500 uses two interrupt queues. one is internal to cx28500 and is controlled exclusively by the dma block. the other is the interrupt queue in shared memory, which is allocated and administered by the host, and written to (filled) by cx28500. upon initialization, the data in the status descriptor is reset to all 0s, indicating the first location for next descriptor, the queue is not full, and no descriptors are currently in the queue. any existing descriptors in the internal queue are discarded. the host must allocate sufficient shared memory space for the interrupt queue. up to 64 k dwords of queue space are accessible by cx28500, setting the upper limit for the queue size. cx28500 requires a minimum of two quadwords of queue space. this sets the lower limit for the queue size. the host must store the pointer to the queue and the length in quadwords of the queue in cx28500 within the interrupt queue descriptor registers. issuing the appropriate host service to cx28500 can do this. as cx28500 takes in the new values, it automatically resets the controller logic as indicated above. this mechanism can also be used to switch interrupt queues wh ile cx28500 is in full operation. 6.3.1.3.2 interrupt de scriptor generation interrupt conditions are detected in both error and non-error cases. cx28500 makes a determination based on channel and device configuration whether reporting of the condition is to be masked or whether an interrupt 30:16 wrptr[14:0] r ? write interrupt pointer. 15-bit qu adword index from start of interrupt queue up to where cx28500 is going to insert the next interrupt descriptors. the host may read this value to get the location of th e last descriptor, which was not served yet, in the queue. as the queue is circular, car e must be taken to ensure roll over at beginning and end of queue. only cx28500 updates this value. the wrptr is a read only bit field. 15 intfull r ? 0: interrupt queue not full?shared memory. 1: interrupt queue full?shared memory. the host writing any value to the readptr clears the intfull status bit. 14:0 rdptr[14:0] r/w ? read interrupt pointer. 15-bit qu adword index from start of interrupt queue up to where the host first unread interrupt descr iptor resides. the host may read this value to get the location of the first d escriptor, which was not served yet, in the queue. as the queue is circular, care must be taken to ensure roll over at beginning and end of queue. only the host updates this value. the readptr is a read/write bit field. note: writing the value of the readptr automatically resets the intfull status bit. therefore, if the value written into rdptr is the same value as was read from this field, it is assumed that the ho st did read all the interrupt descriptors. table 6-19. interrupt status descriptor bit field name host access value description
memory organization 28500-DSH-002-C mindspeed technologies ? 88 mindspeed proprietary and confidential descriptor is to be sent to the host. if the interrupt is not masked, cx28500 generates a descriptor and stores it internally prior to transferring it to the interrupt queue in shared memory. the internal queue is capable of holding 512 descriptors while cx28500 arbitrates to master the pci bus and transfer the descriptors into the interrupt queue in shared memory. as the pci bus is mastered and after descriptors are transferred out to the shared memory, cx28500 updates the interrupt status descriptor. when cx28500 updates the wrpt r field in the interrupt status descriptor, it asserts the pci inta# signal line. if during the transfer of descriptors, the interrupt queue in shared memory becomes full, cx28500 stops transferring descriptors until the host indicates more descriptors can be written out. cx28500 indicates that it cannot transfer more descriptors into shared memory by setting the bit field intfull in the interrupt status descriptor. in cases where the internal queue is full (either because the host queue is full or there was not enough pci bandwidth) and new descriptors are generated, the new descriptors are discarded. cx28500 indicates it has lost interrupts internally by overwriting the bit field ilost in the last interrupt descriptor in the internal queue. the ilost indication represents one or more lost descriptors. 6.3.1.3.3 inta# signal line the host must monitor the inta# signal line at all times. an assertion of this line signifies the updating of the wrptr field in the interrupt status descriptor, indicating that interrupt descriptors have been transferred to the interrupt queue in shared memory from the internal interrupt queue. upon detection of the inta# assertion, the host must perform a direct read of the interrupt status descriptor from within cx28500. this descriptor provides the offset to the location of the first descriptor in the host queue that has not been served, the offset to the location of the last descriptor serviced by the host, and the determination if the queue is full. the inta* signal is deasserted on each read of the interrupt status descriptor. the host applies its interrupt service ro utines to service each of the descriptors. as the host finishes servicing a number of descriptors, it must write the offset to the location of the last serviced descriptor back into the rdptr field of the interrupt status descriptor. a write to this fiel d indicates to cx28500 that the descriptor locations, which were waiting to be serviced, have been serviced and new descriptors can be written. figure 6-1 illustrates the operation of inta*. note: cx28500 continues to write to available space regardless of whether the host updates the rdptr field. the difference between the two interrupt queue pointers rdptr and wrptr indicates the number of interrupts still need to be serviced. when calculating the number of outstanding interrupts, please make sure to t ake care of offsets, or pointers, wraparound.
memory organization 28500-DSH-002-C mindspeed technologies ? 89 mindspeed proprietary and confidential 6.4 global configuration register the global configuration descriptor specifies configuration information applying to the entire device. this register must be programmed before any channel is activated. the only two fields in this register that can be changed while the chip is operating (i.e., not immediately after reset) are the intrs field and the pci_en field. the components and their descriptors are given in ta b l e 6 - 2 0 . figure 6-1. interrupt notification to host table 6-20. global configuration descriptor (1 of 2) bit field name value description 31:15 rsvd 0 reserved 14 pchmode 0 normal operating mode (i.e., not preserve channel mode) 1 preserve channel mode. in this mode requires eccmode = 1: 1. cx28500 transfers in the rx direction the channe l number least significant 8 bits in bits [25:8] in the first dword at st atus buffer descriptor and the channel most significant 2 bits in bits 1:0 of the second dword of the stat us buffer descriptor (i .e., the data pointer). 2. in the tx direction, cx28500 assumes that the fi eld padcount in the buff er descriptor is 0. this enables the host to write any value that helps to better handle buffers circulation into this location knowing that cx28500 does not use padcount and preserve this value in the status buffer descriptor. note that pchmode can be set only when eccmode bit is set. doing othe rwise causes unpredictable behavior. 13 eccmode 0 normal operating mode (i.e., not eccmode) internal logic unserviced interrupt descriptors in the interrupt queue cx28500 host memory interrupt handler interrupt queue inta* 500052_056
memory organization 28500-DSH-002-C mindspeed technologies ? 90 mindspeed proprietary and confidential 1 eccmode: cx28500 supports a 64-bit wide ecc memory as the shared memory. the special behavior includes the following: 1. when updating buffer descriptors in the shared memory, the whole buffer descriptor is written (i.e., 64 bits) rather than the status dword only. 2. when transferring incoming data to shared me mory, any transfer which does not include the end of message is ende d in 64-bit alignment. 3. since this mode makes sense only if the data buffers are 64-bit aligned, cx28500 assumes that the three least significant bits in the da ta pointers of all (i .e., tx and rx) buffer descriptors are 0 regardless of their actual value. cx28500 pres erves the actual value when updating the buffer descriptor with the status . start of receive mess age indication?informs host via som-bit in the receive buffer status descriptor (bit 2 of second dword) that this data buffer contains th e beginning of a message. 12 target_64 ? 0: target (any target that cx28500 can access over the pci) is not guaranteed to allow 64-bit transfers when cx28500 is the master. in this case, a single 64-bit transaction is executed in two 32-bit accesses even when operating in 64-bit pci (for any transaction gr eater than a 64-bit transfer, cx28500 always attempts to transfer 64 bits regardless of the setting of this bit). 1: target (any target that cx28500 can access over the pci) is guaranteed to allow 64-bit transfer. in this case cx28500 always transfers 64 bits whenever possible. 11 target_fbtb ? 0: use the fast back-to-back feature as configured in the pci configuration settings. 1: cx28500 as pci master attempts to fast back-to- back the pci transaction to other targets regardless of pci configuration settings. this bit is defined to force cx28500?s fast back-to -back capability regardless of the pci configuration. the pci specification states that if there is a singl e device in the system that does not support a fast back-to-back transaction as a target, th e fast back-to-back mode is di sabled. setting this bit to 1 instructs cx28500 to ignore the pci configuration settings and execute fast back-to-back transactions when appropriate. the host can set this bit only if cx28500 is always accessing the same target which is capable of fast back to back transactions. this is not a violation of the pci sp ecification, rather it is an implementation of allowed behavior. 10 br ? 0: little-endian storage convention (intel-style). the least significant byte to be stored in and retrieved from the lowest memory address. 1: big-endian storage convention (motorola-style). an example of little-big endian byte ordering is shown in appendix e. 9:1 inttrs[8:0] ? threshold of internal interrupt queue service request. this bit field contains the configuration paramete r of dma internal interrupt service request queue. once the internal queue contains at least one interr upt vector, a low priority dma request is generated toward the internal pci arbiter. this request is removed when the internal queue is empty. if the internal queue contains greater than or equal inttrs numb er of descriptors, a high priority request is generated toward the internal pci arbiter. this requ est is removed when the internal queue contains less than inttrs descriptors. see the description in dm a internal arbiter. this field must never equal 0. 0 pci_en ? 0: pci interrupt disabled?global interrupt mask. 1: pci interrupt enabled. table 6-20. global configuration descriptor (2 of 2) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 91 mindspeed proprietary and confidential 6.5 ebus configuration register the ebus configuration descriptor, defined in ta b l e 6 - 2 1 , specifies the configurat ion parameters for ebus transactions. the host must configure this r egister before any attempt to access the ebus. 6.6 receive path registers receive path registers contain the information necessary to configure the receive direction. this configuration includes registers that are related to the dma block, host interface, registers that control the rslp line processor, and rsiu. table 6-21. ebus configuration register bit field name value description 31:14 rsvd 0 reserved. 13 eclkdiv (1) 0 ebus clock (eclk) has the same frequency as the pci clock (pclk). 1 ebus clock (eclk) has half the frequency of the pci clock (pclk). 12 mpusel 0 expansion bus microprocessor selection?motorola- style. expansion bus supports the motorola-style microprocessor interface and uses motorola signals : bus request (br*), bus grant (bg*), address strobe (as*), read/write (r/w r*), and data strobe (ds*). 1 expansion bus microprocessor selection?intel-style. expansion bus supports the intel-style microprocessor interface and uses intel signals: hold request (hold), hold acknowledge (hlda), address latch enable (ale*) , write strobe (wr*), and read strobe (rd*). 11 ecken 0 expansion bus clock disabled. eclk output is three-stated. 1 expansion bus clock enabled. cx28500 re-drives and inverts pclk input onto eclk output pin. 10:8 alapse[2:0] ? expansion bus address duration. cx28500 ex tends the duration of valid address bits during an ebus address phase to alapse+1 number of eclk periods. th e control lines ale* (intel) or as* (motorola) indicate that the addr ess bits have had the desired setup time. 7:4 blapse[3:0] ? expansion bus access interval. cx28500 waits blapse number of eclk periods immediately after relinquishing the bus. this wait ensures that all the bus grant signals driven by the bus arbiter have sufficient time to be deasserted as a result of bus request signals being deasserted by cx28500. 3:0 elapse[3:0] ? expansion bus data duration. cx28500 extends the duration of valid data bits during an ebus data phase to elapse+1 number of eclk periods. the control lines rd* and wr* (intel) or ds* and r/ wr* (motorola) i ndicate the data bits have had the desired setup time. footnote: (1) after reset, the value of ebus co nfiguration register is 0, except eclkdiv bit fi eld, which is 1. the us er can change the clock division at any time but the ebus clock must be first reset (disabled), i.e., reset ecken bit, and after that a new value of eclkdiv must b e written with ecken set.
memory organization 28500-DSH-002-C mindspeed technologies ? 92 mindspeed proprietary and confidential 6.6.1 rslp channel status register the rslp channel status register is a read only (ro) register. it provides information from rslp block regarding the channel state and status. there is one rslp channel status register for each of cx28500?s channels (i.e., 1024 registers). 6.6.2 rslp channel co nfiguration register the receive channel configuration register contains conf iguration bits applying to the logical channels within cx28500. there are 1024 such registers, one for each channel. the rslp channel configuration descriptor configures aspects of the channel common to all messages passing through the channel. one descriptor exists for each logical channel direction. ta bl e 6 - 2 3 lists the values and descriptions of each channel configuration descriptor. table 6-22. rslp channel status register bit field name host value description 31:4 rsvd r 0 reserved. 3:1 rsvd r don?t care reserved. 0 ractive r 0 channel inactive. the channel has been deactivated due to eith er a service request ch annel deactivation or reset (pci reset or soft chip reset) 1 channel active. the channel has been activat ed by service request channel activation. table 6-23. rslp channel configuration register (1 of 2) bit field name value description 31:30 rprotcol[1:0] 0 transparent. 1hdlc with no fcs. used in islp or full packet forwarding and/or channel m onitoring application. for this mode the sht message detection is disable d. any number of bytes can be transmitted and received within any single message in cluding messages of only one byte. 2 hdlc with fcs16 (fcs?2 bytes). 3 hdlc with fcs32 (fcs?4 bytes). 29 rinv 0 data inversion disabled. 1 data inversion enabled. message is r eceived from siu with polarity cha nge (the inversion is done to all received bits). 28:21 rmask[7:0] ? data mask. only bits with a value of 1 c ontain relevant data (e.g., mask = 10000001, then only bits 0 and 7 contain channel's data). enables the subchanneling feature. 20:5 rsvd 0 reserved. 4:3 maxsel[1:0] 0 message length?disable maximum message length check. 1 message length?use maxfrm1 bit field in the message length descriptor for maximum receive message length limit. 2 message length?use maxfrm2 bit field in the message length descriptors maximum receive message length limit. 3 message length?use maxfrm3 bit field in the message length descriptor for maximum receive message length limit.
memory organization 28500-DSH-002-C mindspeed technologies ? 93 mindspeed proprietary and confidential 6.6.3 rdma buffer allocation register the buffer allocation register configures the internal receive memory. there is one rdma buffer allocation register for each logical channel (i.e., 1024 channels). cx28500?s internal rx memory is a 32-kb dual-port ram, which can be split into 1024 parts, one part for each channel. the allocation granularity is two dwords. for eac h active channel it is required to specify the following:  the starting location of internal data buffer  the ending location of internal buffer  a threshold. this value is triggered when a request from dma needs to be generated to the internal pci arbiter. as soon as the channel?s internal fifo contains more data bytes than this threshold, a request to the rdma to serve this channel is generated, meaning transferring data in the fifo into shared memory. a request to serve this channel is also generated, regardless of the value of the threshold, if a complete message, or an end of message (eom), resides in the channel?s fifo. the host can issue a service request to change the value of this register only when the affected channel is inactive. additionally, internal data buffer a llocation must conform to the following criteria: 1. host must set the buffers so there is no overlap between buffers belonging to different channels. 2. allocated memory segments should not have wraparounds. that is, ending addresses must be greater than starting addresses. 3. the host cannot allocate all of the fifo to one channel. the maximal allocation to one channel is (all fifo) ? 1 quad dwords. each receive channel must be allocated buffer space before the channel can be activated. other important considerations for allocation of internal data buffers include the channel?s data rate and pci latency tolerance. this architecture of configured buffer allocation is completely flexible and allows the host to assign larger fifo buffers to channels that operate at higher rates. for applicatio ns operating high-speed channels (i.e., hyperchanneling) the host can increase the fifo allocation per channel. pci latency tolerance equals the maximum length of time a particular channel can operate normally between pci bus transactions without reaching an internal overflow or underflow condition. pci latency tolerance is primarily dependent on each channel fifo?s buffer size. table 6.6.3 describes the bit fields in the rdma buffer allocation re gister. there are 1024 rdma buffer allocation registers, one for each channel. 2 fcstrans 0 fcs transfer normal. do not transfer received fcs into shared memory along with data message. 1 non-fcs mode. transfer received fcs into shared memory along with data message. in a non-fcs mode a sht message detection is disabled. 1 buffien 0 overflow interrupt disabled. 1 overflow interrupt enabled. 0 idleien 0 chabt, chic, sht interrupt disabled. 1 chabt, chic, sht interrupt enabled. receive only . when receiver detects change to abort code, change to idle code, or too-short message, this bit generates an interrupt to indicate condition. table 6-23. rslp channel configuration register (2 of 2) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 94 mindspeed proprietary and confidential 6.6.4 rdma configuration register this register, defined in ta b l e 6 - 2 5 , controls the per channel rxdma operational mode. there are 1024 such registers, one for each channel. table 6-24. rdma buffer allocation register bit field name value description 31:29 rsvd 0 reserved 28:16 rdma_endad[12:0] (1) ? ending address of internal channel data buffer pointing to dword. 15:13 rsvd 0 reserved 12:0 rdma_startad[12:0] (2) ? starting address of internal channel data buffer general note: 1. one channel maximum must be 32 kb?8 bytes (i.e ., endad = 1ffdh and startad = 000h). 2. endad must be greater than startad (i.e., no rollover). 3. minimal allocation to any channel 4 dwords (i.e., endad ? startad 3). footnote: (1) rdma_endad must be an odd addr ess (i.e., lsb must be 1). (2) rdma_startad must be an even address (i.e., lsb must be 0). table 6-25. rdma channel configuration register (1 of 2) bit field name value description 31:18 rsvd 0 reserved 17 eoceien 0 end of command execution interrupt disabled. 1 end of command execution interrupt enabled. interrupt generated when a command (activate, deactivate or ju mp) execution was completed. 16 inhrbsd (1) 0 inhibit receive buffer status descriptor disable d. at the end of each receive data buffer, overwrite rx buffer descriptor wi th rx buffer status descriptor. 1 inhibit receive buffer status descriptor enable d. at the end of each receive data buffer, do not overwrite rx buffer descriptor wi th rx buffer status descriptor. 15 onrien 0 onr interrupt disabled. 1 onr interrupt enabled. interr upt generated when a new buffer descriptor is read from the host memory and this buffer is host-owned and np bit field is 1. 14 errien 0 error interrupt disabled. 1 error interrupt enabled. interrupt genera ted when end of message detected and error occurred (such as: too-long message, fcs error, and message alignment error or abort condition).
memory organization 28500-DSH-002-C mindspeed technologies ? 95 mindspeed proprietary and confidential 6.6.5 rsiu time slot configuration register 6.6.5.1 time slot map the receive time slot map consists of 4096 time slot descriptors. the entire receive map contains configuration information for 4096 separate time slots. the cx28500?s serial ports support 4096 time slots, which can be configured among the cx28500?s 32 receive serial ports by setting the rsiu time slot pointer assignment. numerous mappings of time slots are possible, multiple time slots can be mapped to a single channel; however each time slot can map to only one channel at a time. for each serial port two time slot maps are required, one for transmit functions and one for receive functions. the two separate maps are configured independently for transmit (tsiu time slot configuration descriptor and tsiu time slot pointer assignment) and receive direction (rsiu time slot configuration descriptor and rsiu time slot pointer assignment). 6.6.5.2 rsiu time slot configuration descriptor for each time slot there is an rsiu time slot configuration descriptor. there are 4096 entries in memory that set the translation between time slots and logical channels for each of cx28500's 32 ports. the actual mapping of these time slot de scriptors to the 32 ports is done by 32 sets of pointer pairs (receive and transmit), one pair set for each port, which indicates the start and the end address of the memory location that belongs to the configured port. time sl ot pointer allocation is de scribed in rsiu time slot pointer allocation. the bit fields of rsiu time slot configuration descriptor include information:  time slot is enabled or disabled  time slot is a full ds0, or subchanneling enabled so that only a part of 64 kbps transports information  indicates if it is the first time slot assigned to the logical channel  logical channel number 13 eomien 0 eom interrupt disabled. 1 eom interrupt enabled. interrupt generated when end of message detected and no error occurred (such as too-long message, fcs error, and message alignment error or abort condition). 12:0 rdma_ trshold[12:0] ? threshold value. as soon as the cha nnel?s internal fifo contains more than or equal number of data dwords than the threshold, a request to the rdma to serve this channel is generated. the value programmed into this field must not exceed the channel?s buffer size, and the threshold must not equal 0. footnote: (1) the normal mode of operation of the cx28500 is to overwrite the rx buffer descriptor with rx buffer status descriptor. this bit is used to inhibit this behavior, so that when it is set, the rx buffer descriptor is not overwritten and the host must rely on interru pts to find out when the cx28500 relinquishes ownership of the buffers. table 6-25. rdma channel configuration register (2 of 2) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 96 mindspeed proprietary and confidential ta bl e 6 - 2 6 specifies the content of each receive time slot configuration descriptor. 6.6.6 rsiu time slot po inter allocation register there is one rsiu time slot pointer allocation descriptor fo r each of cx28500?s 32 serial ports. this register sets the start and end time slot address for the specific co nfigured port. the difference between the configured end and start address specifies the number of time slots allocated for the specified serial port. 6.6.6.1 time slot allocation rules 1. if both pointers point to the same location, this port should be configured to operate in unchannelized mode. this is done by setting the rport_type field in rsiu port configuration register to 0. 2. if there are two, three, or four time slots, the rport_ type field in rsiu port configuration register must be set to 2, 3, or 4 respectively. 3. if there are more than four time slot s, the rport_type field in tsiu port co nfiguration register must be set to either 5, if it is not t1 framing, or 1 if it is. note: for polling to work properly and efficiently, it is mandatory that the first (receive time slot)/last (transmit ti me slot) indications be configured for each channel regardless of the operational mode (i.e., hdlc, transparent, etc.). the polling mechanism in the cx28500 uses these markings as triggering points. when configured correctly, cx28500 polls on a channel once at the selected poll throttle rate instead of polling at ever y time slot allocated to that channel, as in the case of hyperchannels . when a channel consists of only one time slot, as in a dso channel, its corresponding recei ve time slot should have the first_ts bit set. likewise, its corresponding transmit ti me slot should have the last_ts bit set. table 6-26. rsiu time slot configuration descriptor bit field name value description 31:13 rsvd 0 reserved. 12:3 rchannel[9:0] ? logical channel number assigned to the time slot. 2 rts_enable 0 time slot disabled. 1 time slot enabled. 1 rmasken_sb 0 the rmask_sb bit field (rslp channel config uration descriptor) is ignored. all the 8 bits of the time slot are processed. 1 allow data mask for the specified time slot. the bits specified by rmask_sb bit field (rslp channel configuration d escriptor) are processed. 0 rfirst_ts 0 this bit field indicates that the specified time slot is not th e first time slot of the logical channel. 1 this bit field indicates th at the specified time slot is the fi rst time slot of the logical channel. if a serial port is configured to operate in channelized mode, each channel defined to operate over the serial port must have one time slot assign ed to that logical channel that is the first time slot for that channel. in unchannelized mode, this bit must be set in the single time slot assigned. general note: 1. the timeslot map registers have no default values and may be acti ve after reset, so they must be configured before activating the port.
memory organization 28500-DSH-002-C mindspeed technologies ? 97 mindspeed proprietary and confidential 4. if serial port is configured to channelized tsbus mo de, rsiu time slot pointer allocation descriptor is configured to support more than eigh t time slots and the rport_type bit field in rsiu port configuration register must be set to channelized tsbus mode. in the case of unchannelized mode (i.e., the rport_type field in rsiu port configuration register is programmed to 0), cx28500 assumes that only one entry (the one pointed to by startad) is used for this port. this frees the endad pointer to point to any location in the rsiu time slot memory. the differences in these pointers now define the number of time slots to count for polling purposes as described in se ction descriptor polling. ta bl e 6 - 2 7 describes the bit fields in rsiu time slot pointer allocation descriptor. 6.6.7 rsiu port configuration register there is a receive port configuration register for each serial port. it defines how cx28500 interprets and synchronizes the received bit streams associated with the serial port. table 6.6.7 describes the bit fields in rsiu port configuration register. table 6-27. rsiu time slot pointer allocation register bit field name value description 31:28 rsvd 0 reserved. 27:16 rendad_ts[11:0] ? ending location in the receive time sl ot map of the last time slot assigned to this port. 15:12 rsvd 0 reserved. 11:0 rstartad_ts[11:0] ? starting location in the receive time slot map of the fi rst time slot assigned to this port. table 6-28. rsiu port configuration register (1 of 3) bit field name value description 31:14 rsvd 0 reserved. 13 rxenbl (1) 0 receive port disabled. logically resets the serial port, regardless of rts_enable bit field in rsiu time slot configuration descr iptor. this does not affect the bit values in any time slot descriptor. when the serial port becomes inactive, no data is transferred to the slp. 1 receive port enabled. this bit field acts as a logical and between rts_enable bit field in rsiu time slot configurat ion descriptor and time slot. logically, if rts_enable bit field in rsiu time slot configuration descriptor is enabled, it allows all channels with time slot enable bits set to start processing data. this does not affect the bit values in any time slot descriptor. 12 rsvd 0 reserved. general note: writing rxenbl from 0 to 1 forces the port to realign itself to the incoming sync (if channelized) and generate rcofa. in unchannelized port mode, the logical channel mu st be deactivated.
memory organization 28500-DSH-002-C mindspeed technologies ? 98 mindspeed proprietary and confidential 11:9 rport_type 0 unchannelized mode. the user must configure time slot to contain one time slot. 1 t1 mode. this mode includes some number of time slots and one bit of overhead coincident with frame or flywheel sy nc, and that one bit can be masked out. 2 nx64?2 ts. the user must configure the ti me slot map to contain two time slots. 3 nx64?3 ts. the user must configure the time slot map to contain three time slots. 4 nx64?4 ts mode. the user must configure the time slot map to contain four time slots. 5 nx64?the user must configure more than 4 time slots. 6 channelized tsbus mode. the user must confi gure the time slot map to contain at least eight time slots. 7 reserved 8:6 rpollth[2:0] 0 poll throttle. poll at every frame synchronization event. this mechanism can be used to avoid bus saturation when multiple logical ch annels are active and idle and waiting for buffers to service. 1 poll at every 2nd frame synchronization event. 2 poll at every 4th frame synchronization event. 3 poll at every 8th frame synchronization event. 4 poll at every 16th fr ame synchronization event. 5 poll at every 64th fr ame synchronization event. 6 poll at every 128th fr ame synchronization event. 7 poll at every 256th fr ame synchronization event. 5 rsync_edge/ rstuff_edge 0 receiver frame synchronization/ recei ve stuff indication?falling edge. rsync/ rstuff input sampled in on falling edge of rclk. 1 receiver frame synchronization/ recei ve stuff indication?rising edge. rsync/ rstuff input sampled in on rising edge of rclk. 4 rdat_edge 0 receiver data?falling edge. rdat input sampled in on falling edge of rclk. 1 receiver data?rising edge. 3 roof_edge/rtstb_edge 0 receiver out of frame/ tsbus strobe?falling edge. roof/tstb input sampled in on falling edge of rclk. 1 receiver out of frame/ tsbus strobe?ris ing edge. roof/tstb input sampled in on rising edge of rclk. 2 oofabt 0 oof message processing enabled. when oof condition is detected, continue processing incoming data. siu should not report about the oof. 1 oof message processing disabled. 1 oofien 0 out of frame/frame recovery interrupt disabled. 1 out of frame/frame recovery interrupt enabl ed. if oof/frec is detected, generate interrupt indicat ing oof/frec. table 6-28. rsiu port configuration register (2 of 3) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 99 mindspeed proprietary and confidential the bit fields oofien and oofabt are related to each other in the following manner: 1. if both are 0: the signal roof is ignored by cx28500?s rx side. this is the correct programming for tsbus mode or when the roof pin is used as cts or not connected at all. 2. if both are 1: this is the case of oof functionality with oof interrupt. cx28500 interrupts the host and executes the appropriate behavior in the channels affected by the oof. in addition, an oof interrupt is generated and later an oof recovery interrupt when the oof condition ends. 3. if oofabt is 1 and oofien is 0: cx28500 as the case of both 1s except that no interrupt is generated. 4. if oofien is 1 but oofabt is 0: this is the case w here the roof pin is used as a general purpose interrupt pin. cx28500 rx blocks ignore the roof signal but an interrupt to the host is generated when the roof transitions from high to low. 6.6.8 rslp maximum message length register the rslp maximum message length register, defined in ta bl e 6 - 2 9 , can have three separate values for maximum message length: maxfrm1, maxfrm2, and maxfrm 3. their structure is shown in the rslp channel configuration register. the minimum message length is either 1, 3, or 5 depending on protocol mode: no fcs, 16- bit fcs, or 32-bit fcs, respectively. in the case of a short message, data is not transferred into shared memory and is discarded. in addition, an interrupt descriptor is generated toward the host indicating the same error condition. each receive channel either selects one of these message length values or disables message length checking altogether. the maxsel bit field (see table 6-23, rslp channel configuration register ) selects which (if any) register is used for received message length checking. if cx28500 receives a message exceeding the allowed maximum, the current message processing is discontinued and terminates further transfer of data to shared memory. in addition, 0 rcofaien 0 change of frame alignment/recovery from change of frame alignment interrupts disabled. 1 change of frame alignment/recovery from change of frame alignment interrupts enabled. if cofa is detected, generate interrupt indicating cofa. when cofa is recovered from, generate a recovery from cofa interrupt indication. footnote: (1) it is not allowed to change configuration of the port while the port is enabled. there fore, it is not allowed to disable the po rt and change configuation in the same operati on. it is also not allowed to ch ange configuation and enable the port in the same operation. bo th actions need to be split to 2 seperate operations. if the port is active one must first clear the rxenbl bit, and only then write new c onfiguration. if the port is inactive, one must first writ e new configuration with the rxenbl bit cl eared and then re-wri te the register with the same configuration but with the rxenbl bit set. note: for polling to work properly and efficiently, it is mandatory that the first (receive time slot)/last (transmit ti me slot) indications be configured for each channel regardless of the operational mode (i.e., hdlc, transparent, etc.). the polling mechanism in the cx28500 uses these markings as triggering points. when configured correctly, cx28500 polls on a channel once at the selected poll throttle rate instead of polling at ever y time slot allocated to that channel, as in the case of hyperchannels . when a channel consists of only one time slot, as in a dso channel, its corresponding recei ve time slot should have the first_ts bit set. likewise, its corresponding transmit ti me slot should have the last_ts bit set. table 6-28. rsiu port configuration register (3 of 3) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 100 mindspeed proprietary and confidential a receive buffer status descriptor, corresponding to the partially received message, indicates a long message error condition, and an interrupt descriptor is generated toward the host indicating the same error condition. 6.7 transmit path registers transmit path registers contain the information necessary to configure the transmit direction. this configuration includes registers that are related to the dma block, host interface, registers that control the tslp line processor, and tsiu. 6.7.1 tslp channel status register the tslp channel status register, defined in ta b l e 6 - 3 0 , is a read only (ro) register. it provides information from the tslp block regarding the channel state and status. there is one tslp channel status register for each of cx28500?s channels (i.e., 1024 registers). table 6-29. maximum message length register bit field name value description 31:14 rsvd 0 reserved. 13:0 maxfrm[13:0] ? defines a limit for th e maximum number of bytes allowed in a received hdlc message. valid values for the register range from 0 to 16 k-1. the formula to set maxfrm is maxfrm = max allowed message length (bytes) + fcs (bytes)?1. where fcs = 0 for non-fcs mode fcs= 2 byte for hdlc-16 mode fcs = 4 byte for hdlc-32 mode a too long message interrupt is generated when the number of bytes in the processed message exceeds max allowed message length . general note: the host may change the value of maximu m message length register only if the ch annel that uses its value (according to maxsel-bit in the configur ation memory) is inactive. table 6-30. tslp channel status register bit field name host value description 31:4 rsvd r 0 reserved. 3:1 rsvd r don?t care reserved. 0 tactive r 0 channel inactive. the channel has been deactivated due to either a pci reset or soft ch ip reset, or a service request channel deactivation or one of the following transmit errors: txbuff, txcofa. 1 channel active.
memory organization 28500-DSH-002-C mindspeed technologies ? 101 mindspeed proprietary and confidential 6.7.2 tslp channel configuration register the transmit channel configuration register contains configuration bits applying to the logical channels within cx28500. there are 1024 such registers, one for each channel. the tslp channel configuration descriptor configures aspects of the channel common to all messages passing through the channel. one descriptor exists for each logical channel direction. ta bl e 6 - 3 1 lists the values and descriptions of each channel configuration descriptor. 6.7.3 tdma buffer allocation register the buffer allocation register configures the internal receive memory. there is one tdma buffer allocation register for each logical channel (i.e., 1024 channel). cx28500?s internal tx memory is a 32-kb dual ram, which can be split into 1024 parts, one part for each channel. the allocation granularity is two dword. for each active channel it is required to specify the following:  the starting location of internal data buffer  the ending location of internal buffer  a threshold. this value is triggered when a request from dma must be generated to the internal pci arbiter. as soon as the channel?s internal fifo contains less data bytes than the threshold, an attempt to read data from shared memory is made. the threshold indicates and determines when the txdma begins transfer of data to the txslp. hence, it indicates when a new transmission of a new message can start. if the buffer contains less table 6-31. tslp channel configuration register bit field name value description 31:30 tprotocol[1:0] 0 transparent. 1hdlc with no fcs. used in islp or full packet forwarding and/or channel m onitoring application. for this mode, the sht message detection is disabled. any number of bytes can be transmitted and received within any single message in cluding messages of only one byte. 2 hdlc with fcs16 (fcs?2 bytes). 3 hdlc with fcs32 (fcs?4 bytes). 29 tinv 0 data inversion disabled. 1 data inversion enabled. message is transferred to the siu with polarity change (the inversion is done to all bits passed). 28:21 tmask[7:0] ? an 8-bit data mask. each bit with the value of 1 should contain data when the relevant time slot is transmitted (e.g., mask = 10000001, message data is tr ansmitted only on bits 0 and 7, the other bits are discarded by the receiver). 20:3 rsvd 0 reserved. 2 padj 0 pad count adjustment disabled. no adjustment is made to the number of pad fill bytes if zero insertions is detected. 1 pad count adjustment enabled. 1 buffien 0 underrun interrupt disabled. 1 underrun interrupt enabled. 0 eomien 0 eom interrupt disabled. 1 eom interrupt enabled. interrupt generated upon end of message detection when transferring data from the tslp to the tsiu.
memory organization 28500-DSH-002-C mindspeed technologies ? 102 mindspeed proprietary and confidential data than the threshold, no transfer is generated unless there is already an eom, meaning a whole message, in the internal fifo. the host can issue a service request to change the value of this register only when the affected channel is inactive. additionally, internal data buffer a llocation must conform to the following criteria: 1. host must set the buffers so there is no overlap between buffers belonging to different channels. 2. allocated memory segments should not have wraparounds. that is, ending addresses must be greater than starting addresses. 3. the host cannot allocate all of the fifo to one channel. the maximal allocation to one channel is (all fifo) ? 1 quad dwords. each transmit channel must be allocated buffer space before the channel can be activated. other important considerations for allocation of internal data buffers include the channel?s data rate and pci latency tolerance. this architecture of configured buffer allocation is completely flexible and allows the host to assign larger fifo buffers to channels that operate at higher rates. for applicatio ns operating high-speed channels (i.e., hyperchanneling) the host can increase the fifo allocation per channel. pci latency tolerance equals the maximum length of time a particular channel can operate normally between pci bus transactions without reaching an internal overflow or underflow condition. pci latency tolerance is primarily dependent on each channel fifo?s buffer size. ta bl e 6 - 3 2 describes the bit fields in tdma buffer allocation register. there are 1024 tdma buffer allocation registers, one for each channel. 6.7.4 tdma configuration register this register, defined in ta b l e 6 - 3 3 , controls per channel the txdma operational mode. there are 1024 such registers, one for each channel. table 6-32. tdma buffer allocation register bit field name value description 31:29 rsvd 0 reserved. 28:16 tdma_endad[12:0] (1) ? ending address of internal channel data buffer. 15:13 rsvd 0 reserved. 12:0 tdma_startad[12:0] (2) ? starting address of internal channel data buffer. general note: 1. one channel maximum must be 32 kb-1 quad-wor ds (i.e., endad = 1ff eh and startad = 0000h). 2. endad must be greater than startad (i.e., no rollover). 3. minimal allocation to any channel 4 dwords (i.e., endad ? startad 3). footnote: (1) tdma_endad must be an odd addr ess (i.e., lsb must be 1). (2) tdma_startad must be an even address (i.e., lsb must be 0). table 6-33. tdma channel configuration register (1 of 2) bit field name value description 31:17 rsvd 0 reserved. 16 eoceien 0 end of command execution interrupt disabled. 1 end of command execution interrupt enabled. interrupt generated when a command (activate, deactivate or ju mp) execution was completed.
memory organization 28500-DSH-002-C mindspeed technologies ? 103 mindspeed proprietary and confidential 6.7.5 tsiu time slot configuration register 6.7.5.1 time slot map the transmit time slot map consists of 4096 time slot descriptors. the entire transmit map contains configuration information for 4096 separate time slots. the cx28500?s serial ports support 4096 time slots, which can be configured among the cx28500?s 32 transmit serial ports by setting the tsiu time slot pointer assignment. numerous mappings of time slots are possible, and multiple time slots can be mapped to a single channel; however each time slot can map to only one channel at a time. for each serial port, two time slot maps are required: one for transmit functions and one for receiv e functions. the two separate maps are configured independently for transmit direction (tsiu time slot configuration descriptor and tsiu time slot pointer assignment) and receive direction (rsiu time slot configuration descriptor and rsiu time slot pointer assignment). these pointers are described in ta b l e 6 - 3 4 . ta bl e 6 - 3 5 specifies the content of each entry. 6.7.5.2 tsiu time slot configuration descriptor there is an tsiu time slot configuration descriptor for each time slot (refer to ta bl e 6 - 3 4 ). there are 4096 entries in memory that set the translation between time slots and logical channels for each of cx28500's 32 ports. the actual mapping of these time slot de scriptors to the 32 ports is done by 32 sets of pointer pairs (receive and transmit), one pair set for each port, which indicates the start and the end address of the 15 inhtbsd (1) 0 inhibit transmit buffer status descriptor disabled. at the end of each transmit data buffer, overwrite tx buffer descriptor with tx buffer status descriptor. 1 inhibit transmit buffer status descriptor enable d. at the end of each transmit data buffer, do not overwrite tx buffer descriptor with tx buffer status descriptor. 14 onrien 0 onr interrupt disabled. 1 onr interrupt enabled. interrupt generated wh en a new buffer descriptor is read from the host memory, the ownership bit state is owned by the host, and the np bit field is 1, and the dma is in mid-message. 13 autoenable 0 automatic fetch feature disabled. 1 automatic fetch feature enable d. attempts fetching of more shared memory as soon as it has 32 free dwords in the channel buffer. 12:0 tdma_trshold[12:0] ? threshold value. the value programmed into this field must not exceed the channel?s buffer size. the threshold value indicates the following: 1. when the buffer contains less data than the threshold, a request to the tdma to serve this channel is generated. an attempt to read more data from the host memory is made. 2. when a transmission of a new message can start. when the buffer contains less data than the threshold, no new transm ission starts unless there is a whole message already in the internal fifo. footnote: (1) the normal mode of operation of the cx28500 is to overwrite the tx buffer descriptor wi th tx buffer status descriptor. this bit is used to inhibit this behavior, so that when it is set, the tx buffer descri ptor is not overwritten and the host must rely on interru pts to find out when the cx28500 relinquishes ownership of the buffers. table 6-33. tdma channel configuration register (2 of 2) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 104 mindspeed proprietary and confidential memory location that belongs to the configured port. time sl ot pointer allocation is described in tsiu time slot pointer allocation. the bit fields of tsiu time slot configuration descriptor include information:  time slot is enabled or disabled  time slot is a full ds0, or subchanneling enabled so that only a part of 64 kbps transports information  indicates if it is the last time slot assigned to the logical channel  logical channel number (1024) 6.7.6 tsiu time slot pointer assignment register there is one tsiu time slot pointer allocation descriptor for each of cx28500?s 32 serial ports. this register, defined in ta bl e 6 - 3 5 , sets the start and end time slot address for the specific configured port. the difference between the configured end and start address specifies the number of time slots allocated for the specified serial port. note: for polling to work properly and efficiently, it is mandatory that the first (receive time slot)/last (transmit ti me slot) indications be configured for each channel regardless of the operational mode (i.e., hdlc, transparent, etc.). the polling mechanism in the cx28500 uses these markings as triggering points. when configured correctly, cx28500 polls on a channel once at the selected poll throttle rate instead of polling at ever y time slot allocated to that channel, as in the case of hyperchannels . when a channel consists of only one time slot, as in a ds0 channel, its corresponding r eceive time slot should have the first_ts bit set. likewise, its corresponding transmit ti me slot should have the last_ts bit set. table 6-34. tsiu time slot configuration descriptor bit field name value description 31:13 rsvd 0 reserved. 12:3 tchannel [9:0] ? channel assigned to the time slot. 2 tts_enable 0 time slot disabled. 1 time slot enabled. 1 tmasken_sb 0 do not use the data mask for this time slot for this channel. this means all 8 bits are processed. (subchanneling disabled) 1 allow using the data mask for this time slot for this channel. thi s means only the bits specified by the data mask are processed. (subchanneling enabled) 0 tlast_ts 0 indicates that this is not the last time slot where this channel appears in this frame. 1 indicates that this is the last time slot where this channel appears in the frame. if a serial port is configured to operate in ch annelized mode, each channel defined to operate over the serial port must have one time slot assigne d to that logical cha nnel that is defined as the last time slot for that channel. in uncha nnelized mode, this bit must be set in the single time slot assigned. general note: 1. the timeslot map registers have no default values and may be acti ve after reset, so they must be configured before activating the port.
memory organization 28500-DSH-002-C mindspeed technologies ? 105 mindspeed proprietary and confidential 6.7.6.1 time slot allocation rules 1. if both pointers point to the same location, this port should be configured to operate in unchannelized mode. this is done by setting the prottyp field in tsiu port configuration register to 0. 2. if there are two, three, or four time slots, the porttyp field in tsiu port configuration register must be set to 2, 3, or 4, respectively. 3. if there are more than four time slots, the porttyp field in rsiu port configuration register must be set to either 5, if it is not t1 framing, or 1 if it is. 4. if serial port is configured to channelized tsbus mo de, rsiu time slot pointer allocation descriptor is configured to support more than eigh t time slots and the tprot_type bit field in rsiu port configuration register must be set to channelized tsbus mode. in the case of unchannelized mode (i.e., the porttyp field in tsiu port configuration register is programmed to 0), cx28500 assumes that only one entry (the one pointed to by startad) is used for this port. this frees the endad pointer to point to any location in the tsiu time slot memory. the differences in these pointers now define the number of time slots to count for polling pur poses as described in se ction descriptor polling. 6.7.7 tsiu port configuration register there is one tsiu port configuration register per port (see table 6.7.7 ). this register defines how cx28500 generates and synchronizes the transmit bit streams associated with the port. there are 32 such registers, one for each port. table 6-35. tsiu time slot pointers register bit field name value description 31:28 rsvd 0 reserved. 27:16 tendad_ts[11:0] ? ending location in the transmit time slot map of the last time slot assigned to this port. 15:12 rsvd 0 reserved. 11:0 tstartad_ts[11:0] ? starting location in the transmit time slot map of the first time slot assigned to this port. general note: endad must be startad (meaning, no wraparound). table 6-36. tsiu port configuration register (1 of 3) bit field name value description 31:14 rsvd 0 reserved. 13 txenbl (1) 0 transmit port disabled. logically resets the time slot, regardless of tts_enable bit field in tsiu time slot configurati on descriptor. this does not affect the bi t values in any time slot descriptor. 1 transmit port enabled. this bit field acts as a logi cal and between tts_enable bit field in tsiu time slot configurat ion descriptor and time slot. logically, if tts_enable bit field in tsiu time slot configuration descr iptor is enabled, it allows all channels with time slot enable bits set to start pro cessing data. this does not af fect the bit values in any time slot descriptor. 12 rsvd 0 reserved.
memory organization 28500-DSH-002-C mindspeed technologies ? 106 mindspeed proprietary and confidential 11:9 tport_type 0 unchannelized mode. the user must configure time slot to contain one time slot. 1 t1 mode. this mode implies 24 time slots and t1 signalling. the user must configure the time slot map to contain exactly 24 time slots. 2 nx64?2 ts. the user must configure the ti me slot map to contain two time slots. 3 nx64?3 ts. the user must configure the time slot map to contain three time slots. 4 nx64?4 ts mode. the user must configure the time slot map to contain four time slots. 5 nx64?the user must configure more than 4 time slots. 6 channelized tsbus mode. the user must configure the ti me slot map to contain at least eight time slots. 7 reserved 8:6 tpollth[2:0] 0 poll throttle. poll at every frame synchronization event. this mechanism can be used to avoid bus saturation when multiple logical channels are ac tive and idle and waiting for buffers to service. 1 poll at every 2nd frame synchronization event. 2 poll at every 4th frame synchronization event. 3 poll at every 8th frame synchronization event. 4 poll at every 16th frame synchronization event. 5 poll at every 64th frame synchronization event. 6 poll at every 128th frame synchronization event. 7 poll at every 256th frame synchronization event. 5 tsync_edge/ tstuff_edge 0 transmitter frame synchronization/receive st uff indication?falling edge. rsync/rstuff input sampled in on falling edge of rclk. 1 transmitter frame synchronization/receive stu ff indication?rising edge . rsync/rstuff input sampled in on rising edge of rclk. 4 tdat_edge 0 transmitter data?falling edge. tdat output driven on falling edge of tclk. 1 transmitter data?rising edge. 3 cts_edge/ stb_edge 0 transmitter cts/tsbus strobe?falling edge. cts/stb input is sampled on the falling edge of tclk. 1 transitter cts/tsbus strobe?rising edge. cts/stb input is sampled on the rising edge of tclk. 2 ctsenb 0 cts disabled. this bit is ignored when the port is operating in tsbus mode. 1 cts enabled. this bit is ignored when the port is operating in tsbus mode. 1 tritx 0 transmit three-state disabled. wh en a channel port is enabled, but a time slot within the port is not mapped via the time slot map, the transmitter outputs a logic 1 on the output data signal. 1 transmit three-state enabled. when a port is enabled, but a time slot within the port is not mapped via the time slot map, the transmitter three-states the output data signal. table 6-36. tsiu port configuration register (2 of 3) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 107 mindspeed proprietary and confidential 0 tcofaien 0 change of frame alignment/recovery from change of frame alignment interrupts disabled. 1 change of frame alignment/recovery from change of frame alignment interrupts enabled. if cofa is detected, generates an interrupt indicating cofa. wh en cofa is recovered from, generates a recovery from cofa interrupt indication. footnote: (1) it is not allowed to change configuration of the port while the port is enabled. there fore, it is not allowed to disable the po rt and change configuation in the same operati on. it is also not allowed to ch ange configuation and enable the port in the same operation. bo th actions need to be split to 2 separate operations. if the port is active one must first clea r the txenbl bit, and only then write new c onfiguration. if the port is inactive, one must first writ e new configuration with the txenbl bit cleared and then re-write the register with the same configuration but with the txenbl bit set. note: for polling to work properly and efficiently, it is mandatory that the first (receive time slot)/last (transmit ti me slot) indications be configured for each channel regardless of the operational mode (i.e., hdlc, transparent, etc.). the polling mechanism in the cx28500 uses these markings as triggering points. when configured correctly, cx28500 polls on a channel once at the selected poll throttle rate instead of polling at ever y time slot allocated to that channel, as in the case of hyperchannels . when a channel consists of only one time slot, as in a ds0 channel, its corresponding r eceive time slot should have the first_ts bit set. likewise, its corresponding transmit ti me slot should have the last_ts bit set. table 6-36. tsiu port configuration register (3 of 3) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 108 mindspeed proprietary and confidential 6.8 receive and transmit data structures figures 6-2 and 6-3 illustrate the receive and transmit data st ructures used for data communication between cx28500 and the host. figure 6-2. transmit data structures transmit base address head pointer (tbahp) transmit head pointer (thp) current message descriptor (md) md transmit internal message processing table (timpt) message descriptor head pointer (mdhp) mdhp (ch #i) mdhp buffer status descriptor (bsd) bsd bsd transmit head pointer ta b l e (thpt) transmit message descriptor table (tmdt ch #0) transmit message descriptor table (tmdt ch #i) 0 1023 0 1023 . . . . . . . . . . . . . . . . . . . 0 4095 . . . . . . . data buffer data buffer bsd bsd bsd 0 4095 . . . . . . . data buffer data buffer 12 bit internal shared memory base address head pointer (bahp) thp footnote: (1) bahp must be dword aligned [1:0] = 00. (2) mdhp must be 64-bit aligned [2:0] = 000. (1) (2) (2) 500052_057
memory organization 28500-DSH-002-C mindspeed technologies ? 109 mindspeed proprietary and confidential 6.8.1 transmit message path 6.8.1.1 shared memory 6.8.1.1.1 transmit head pointer table (thpt) this table is allocated and initialized by the host. this table is an array of 1024 entries (one for each channel) which contain the message descriptor head pointer address for each logical channel configured in the application. each message descriptor head pointer points to the starting address of the transmit message descriptor table associated with the respective channel. figure 6-3. receive message data structures receive base address head pointer (tbahp) receive head pointer (rhp) current message descriptor (md) md receive internal message processing table (rimpt) message descriptor head pointer (mdhp) mdhp (ch #i) (2) mdhp (2) buffer status descriptor (bsd) bsd bsd receive head pointer ta b l e (rhpt) receive message descriptor table (rmdt ch #0) receive message descriptor table (rmdt ch #i) 0 1023 0 1023 . . . . . . . . . . . . . . . . . . 0 4095 . . . . . . . data buffer data buffer bsd bsd bsd 0 4095 . . . . . . . data buffer data buffer 12 bit internal shared memory base address head pointer (bahp) (1) rhp 500052_058 footnote: (1) bahp must be dword aligned [1:0] = 00. (2) mdhp must be 64-bit aligned [2:0] = 000. (3) for both tx and rx directions, eccmode = 1 requires 64-bit aligned data buffer pointers. additionally, for the rx direction, receive data buffer length must be an integer multiple of 8 bytes. for both tx and rx directions, eccmode = 0 allows byte- aligned data buffer pointers and data buffer length. (3)
memory organization 28500-DSH-002-C mindspeed technologies ? 110 mindspeed proprietary and confidential 6.8.1.1.2 transmit message descriptor table (tmdt) for each channel, the host allocates the tmdt table. this table is an array which contains up to 4096 entries. each entry contains the buffer status descriptor, plus a pointer to the data buffer. both tmdt and data buffer are allocated in shared memory and initialized by the host during th e driving initialization process. after channel activation service request, the buffer status descriptor (bsd) is updated by cx28500, after processing the current buffer. 6.8.1.1.3 data buffer location in shared memory where data is stored. 6.8.2 receive message path 6.8.2.1 shared memory 6.8.2.1.1 receive head pointer table (rhpt) this table is allocated and initialized by the host. this table is an array of 1024 entries (one for each channel) which contain the message descriptor head pointer address for each logical channel configured in the application. each message descriptor head pointer points to the starting address of the receive message descriptor table associated with the respective channel. 6.8.2.1.2 receive message descriptor table (rmdt) the host allocates the rmdt table for each channel. this table is an array which contains up to 4096 entries. each entry contains the buffer status descriptor, plus pointer to the data buffer. both rmdt and data buffer are allocated in shared memory and initia lized by the host during the driving initialization process. after channel activation service request, the buffer status descriptor (bsd) is updated by cx28500, after processing the current message. 6.8.2.1.3 data buffer location in shared memory where data is stored. 6.8.3 internal memory 6.8.3.1 transmit path 6.8.3.1.1 transmit base address head pointer (tbahp) (config_wr) this register contains the base address of the transmit head pointer table update during the config_wr srq. 6.8.3.1.2 transmit internal message processing table (timpt) for each channel?s message descriptor (md) table, cx2850 0 maintains a pointer to its first md copied from the head pointer table and a pointer (actually the offset from the starting address of the current md being processed). the length of transmit message descriptor table is given by the fact that the md is a 12-bit field in transmit internal message processing table (timpt).
memory organization 28500-DSH-002-C mindspeed technologies ? 111 mindspeed proprietary and confidential 6.8.3.2 receive path 6.8.3.2.1 receive base address head pointer (rbahp) (config_wr) this register contains the base address of the receive head pointer table update during the config_wr srq. 6.8.3.2.2 receive internal me ssage processing table (rimpt) for each message descriptor (md) table, cx28500 maintains a pointer to its first md copied from the head pointer table and a pointer (actually the offset from the starting address of the current md being processed). the length of receive message descr iptor table is given by the fact that the md is a 12-bit field in receive internal message processing table (rimpt). 6.8.4 head pointer table and its content there are two cx28500 internal registers that contain the address of the transmit and receive head pointer table (i.e., thpt and rhpt). these registers are updated with the values of thpt and rhpt during config_wr service request cycle. the content of tbahp or rbahp register is described in ta bl e 6 - 3 7 . the content of each register (tbahp or rbahp) contains the starting address of the transmit head pointer table (thpt) or receive head pointer table (rhpt), respectively. the content of each thpt or rhpt table contains the address of the message descriptor head pointer table, for each independent channel (see ta bl e 6 - 3 8 ). 6.8.5 message descriptor (md) a message descriptor defines one data buffer where all or part of a message is stored in shared memory. by allocating a number of message descriptors to the message descriptor table, numerous data buffers can be linked together to support high-speed data links or large messages spread across a number of smaller data buffers. depending on the transmission and reception rate of individual channels, the numbers and sizes of message buffers can vary between channels and/or applications. for high-speed channels, more and larger buffers can be table 6-37. transmit and receive base address head pointer (tbahp and rbahp) content bit field name value description 31:2 bahptbl[29:0] ? these 30 bits are appended with 00b to fo rm a dword-aligned 32-bit address. this address points to the first head pointer descriptor in the table of head pointers descriptors in the host shared memory. 1:0 bahptbl[1:0] 00 ensures dword alignment table 6-38. transmit and receive head pointer table (thpt and rhpt) content bit field name value description 31:3 mdhp[28:0] ? these 29 bits are appended with 000b to form a 64-bit aligned a ddress. this address points to the first message descriptor in the table of message descr iptors associated with a specific channel as illustrated in figure 6-3, receive message data structures . 2:0 mdhp[2:0] 000 ensures 64-bit alignment
memory organization 28500-DSH-002-C mindspeed technologies ? 112 mindspeed proprietary and confidential employed to provide ample data storage while the host processes each message in the table of messages. for low-speed channels, fewer and smaller buffers can be employed, because the host may be able to process each message faster, and the need to store messages is lessened. multiple smaller data buffers can store one large message. in utilizing multiple buffers, the importance of keeping the sequence of data buffers in order is obvious. cx28500's operation a llows for the following:  multiple message descriptor tables  multiple and variable size buffers within a message descriptor table  multiple buffers storing a single message  sequencing of individual data buffers for a multi-buffer message a message descriptor is intentionally designed to be usable by both the transmit and receive functions in cx28500. in providing this symmetry, a mechanism known as self-ser vicing buffers is available. this mechanism allows the reuse of a single descriptor for both the transmit and receive portions of a channel, and is designed for diagnostics and loop-back capabilit ies. for details, see self-servicing buffers . there are up to 4096 entries in transmit or receive message descriptor table (tmdt and rmdt) each of 2 dwords. each entry in this table contains either a buffer descriptor (bd) which is written by the host or a buffer status descriptor (bsd) which is written by cx28500. th e bd and bsd represent one dword from the content of tmdt or rmdt; the other dword contains the address of the data buffer (see ta b l e 6 - 3 9 ). cx28500 checks certain data from a message descriptor before processing the associated data buffer. when a data buffer is completely processed (either transmitted or received), cx28500 overwrites the buffer descriptor field (the first dword in a message descriptor) with a buffer status descriptor, if this is allowed for the related channel. for details see ta bl e 6 - 2 5 , rdma channel configuration register and ta b l e 6 - 3 3 , tdma channel configuration register . the buffer status descriptor specifies the number of bytes transferred, an end of message indicator, and a buffer onr-bit indicator that assigns control of associated buffers back to the host. the onr-bit mechanism transfers control of a data buffer between cx28500 and the host. the message descriptor can be assigned before an associated data buffer is allocated in memory. in this case, cx28500 is instructed to poll the contents of the buffer descriptor until the host grants ownership of a data buffer to cx28500. after cx28500 processes the data buffer, it grants the ownership back to the host. if the onr-bit indicates that cx28500 does not own the next buffer and if np = 1 (pollin g is not enabled) and in mid-message, then this is an error condition. cx28500 generates onr interrupt and all the dma handling is table 6-39. transmit or receive message descriptor table (tmdt) or (rmdt) content byte offset field name dwords bytes 00h buffer descriptor (host writes) buffer status de scriptor (cx28500 writes) 1 4 04h data pointer 14 total 28 note: when operating in ecc mode, if configured to write buffer status descriptor, cx28500 writes both the status descripto r and its attached data buffer pointer. this is necessary in order to perform a 64-bit write transaction. the pointer value is the same value that was read by cx28500.
memory organization 28500-DSH-002-C mindspeed technologies ? 113 mindspeed proprietary and confidential suspended for the channel. the host must use the host service mechanism (channel activation or channel jump commands) in order to continue dma handling for the channel. the onr-bit mechanism prevents cx28500 from processing the same buffer twice without intervention from the host. additionally, the host can append additional information beyond the end of a data buffer as long as the longest message length can be fitted first into the data buffer. in the case of additional information, it is ignored. for simplicity, the following discussi on is made in reference to one channel. each channel is serviced independently of another channel, and separate message descriptor tables are maintained for each supported channel. similarly, both transmit and receive sections of a channel service the descriptor tables identically, and separate message descriptor tables are maintained for each section. also, the size of data fields in the descriptors is identical; however, the layout of fields between receive and transmit descriptors is different. 6.8.6 buffer descriptors the buffer descriptor (bd) resides in the shared memory and is fetched by cx28500 each time a new data buffer is required. all buffer descript ors include the following fields:  owner indicator bit (onr)  no poll/poll indicator (np)  end of buffer interrupt enable (eobien)  last md in the table (last)  buffer length (blen) the onr bit is a generic term for any descriptor. in a tran smit buffer descriptor it is generically called cx28500- owned. in a receive buffer descriptor it is generically called host-owned. the names are different to indicate that the active sense of the onr bit is different between transmit and receive functions. in addition to the above list of fields, transmit buffer descriptors include the following fields:  end of message indicator (eom)  idle code selection (ic)  pad count (padcnt) ic and padcnt are valid only when eom = 1. tables 6-40 and 6-41 list the transmit and receive buffer descriptors and definitions. table 6-40. transmit buffer descriptor (1 of 2) bit field name value description 31 onr 0 host owns buffer. channel is to remain in idle mode while polling this bit periodically (if np = 0) until host relinquishes control to cx28500 by setting onr = 1. 1 cx28500 owns buffer. continue processing data buffer normally. 30 np 0 poll enabled. if onr = 0, host-owned, cx28500 polls the message descriptor periodically while in idle mode until onr = 1. 1 poll disabled. if onr = 0, then enter suspend mode and wait for a channel activate or jump host service from host.
memory organization 28500-DSH-002-C mindspeed technologies ? 114 mindspeed proprietary and confidential 29 eom 0 end of message indicator clear?this is not the last buffer for the current message. 1 end of message indicator se t?this is the last buffer for the current message. 28 eobien 0 end of buffer interrupt disable d. when the last data byte was taken from this buffer, an eob interrupt is not generated. 1 end of buffer interrupt enabled. wh en the last data byte was taken from this buffer, or the bsd is written, an eob interrupt is generated. 27:26 ic[1:0] (1) 0 idle code select?if the protocol is hdlc, the idle code select is 7eh. if the protocol is transparent, the idle code select is ffh. 1 idle code select?if the protocol is hdlc, the idle code select is ffh. if the protocol selection is transparent, the idle code select is 7eh. 2 idle code select?00h. 3 reserved. 25:18 padcnt[7:0] (2) rsvd [7:0] ? pad count/reserved. when operating in normal mode (i.e., not in preserve channel mode) this field is treated as padcount. padcnt indicates the minimum number of idle codes to be inserted between the closing flags and the next opening flag (7eh). if padcnt = 2 and ic = 1, for example, cx28500 outputs the bit pattern 7eh..ffh..ffh..7eh. there is no indication by cx28500 if more than padcnt number of idle codes are inserted. when operating in preserve channel mode, this field is treated as a reserved field whose bits are preserved in the transmit buffer descriptor. 17:15 abort 0 packet should be transmitted and end correctly. 1-7 packet transmission should end wi th abort sequence when eom = 1. 14 txlast 0 this is not the last md in this message descriptor table. 1 this is the last md in th is message descriptor table. 13:0 blen[13:0] (3) ? buffer length. the number of bytes in data buffer to be transmitted. in general, this would equal the allocated buffer size. if eom = 0 and blen = 0, the dma ignores this bd and skips to the next one. if eom = 1, blen = 0, abort = 0, and prior not-eo m data buffer, the dma completes transmission of the prior buffer. footnote: (1) ic field is processed and used by cx28500 only when eom is set (i.e., only in th e last buffer descriptor of a message). (2) padcnt field is processed and used by cx28500 only when eom is set (i.e., only in th e last buffer descript or of a message). (3) the combination of blen = 0 and eom = 0 in the middle of a message is not allowed. table 6-41. receive buffer descriptor (1 of 2) bit field name value description 31 onr 0 cx28500 owns buffer. continue processing data buffer normally. 1 host owns buffer. channel is to remain in idle mode while polling this bit periodically (if np = 0) until host relinquishes control to cx28500 by setting onr = 0. 30 np 0 poll enabled. if onr = 1, ho st-owned, cx28500 polls message descriptor periodically until onr = 0. 1 poll disabled. if onr = 1, then enter suspend mo de and wait for a channel activate or jump host service from host. 29 rsvd 0 reserved. table 6-40. transmit buffer descriptor (2 of 2) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 115 mindspeed proprietary and confidential 6.8.7 buffer status descriptor the buffer status descriptor (bsd) contains information regarding the data buffer processing. if bsd updates are allowed, the information is written over the buffer descriptor. the bsd includes the following bit fields:  owner indicator bit (onr)  end of message indicator (eom)  last md in the table (last)  data length (dlen) the receive buffer status descriptor contains an error status (error) bit field. the design of bsd and bd in the same location allows cx28500 to self-service the buffers without host intervention. see the self servicing mechanism chapter. tables 6-42 and 6-43 list the transmit and receive buffer status descriptors and their descriptions. 28 eobien 0 end of buffer in terrupt disabled. when the last data byte is put into this buffer, an eob interrupt is generated. 1 end of buffer interrupt enabled. when the last data byte is put into this buffer, an eob interrupt is generated. 27:26 rsvd 0 reserved. 25:18 rsvd/ chan [7.0] 0 when operating in normal mode (i.e., not preserve channel mode as indicated by bit pchmode in global configuration descriptor) th is field is reserved. when operating in preserve channel mode, this field is used by cx28500 to transfer the least significant 8 bits of the channel number. the most significant bits are transf erred to the data pointer. 17:15 rsvd 0 reserved 14 rxlast 0 this is not the last md in this message descriptor table. 1 this is the last md in this message descriptor table. 13:0 blen[13:0] ? buffer length. actual number of received data bytes might be less than this. this number indicates how many will fit into the data buffer. if blen=0, the rdma ignores this md and skips to the next one. note: while operating in ecc mode, if configured to update the buffer status descriptor, the cx28500 writes both the bsd and the data buffer pointer. this is required in order to perform a 64-bit pci write transaction. table 6-42. transmit buffer status descriptor (1 of 2) bit field name value description 31 onr 0 host owns buffer. channel is to remain in idle mode while polling this bit periodically (if np = 0) until host relinquishes control to cx28500 by setting onr = 1. 1 cx28500 owns buffer. continue processing data buffer normally. 30 np 0 poll enabled. if onr = 0, host-owned, cx28500 polls the message descriptor periodically while in idle mode until onr = 1. 1 poll disabled. if onr = 0, then enter suspend mode and wait for a channel activate or jump host service from host. table 6-41. receive buffer descriptor (2 of 2) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 116 mindspeed proprietary and confidential 29 eom 0 end of message indicator clear?this is not the last buffer for the current message. 1 end of message indicator set ?this is the last buffer for the current message. 28 eobien 0 end of buffer interrupt disabled . when the last data byte is taken fr om this buffer, an eob interrupt is not generated. 1 end of buffer interrupt enabled. when the last data byte is taken from this buffer, an eob interrupt is generated. 27:26 ic[1:0] 0 idle code select?if the protocol is hdlc, th e idle code select is 7eh. if the protocol selection is transparent, the idle code select is ffh. 1 idle code select?if the protocol is hdlc, the idle code select is ffh. if the protocol selection is transparent, the idle code select is 7eh. 2 idle code select?00h. 3 reserved. 25:18 padcnt[7:0] rsvd [7:0] ? pad count/reserved. when operating in normal mode (i.e., not in preserve channel mode) this field is treated as padcount. padcnt indicates the minimum number of idle codes to be inserted between the closing flags and the next opening flag (7eh). if padcnt = 2 and ic = 1, for example, cx28500 outputs the bit pattern 7eh..ffh..ffh..7eh. there is no indication by cx28500 if more than padcnt number of idle codes are inserted. when operating in preserve channel mode, this field is treated as a reserved field whose bits are preserved in the transmit buffer status descriptor. 17:15 abort 0 packet should be transmitted and end correctly. 1-7 packet transmission shoul d end with abort sequence. 14 txlast 0 this is not the last md in this message descriptor table. 1 this is the last md in th is message descriptor table. 13:0 blen[13:0] ? buffer length. the number of bytes in data buffer to be transmitted. in general, this would equal the allocated buffer size. if eom = 1 and blen = 0, cx2 8500 is requested to generate hdlc abort sequence. if eom = 0 and blen = 0, the dma ignores this bd and skips to the next one. table 6-43. receive buffer status descriptor bit field name value description 31 onr 0 cx28500 owns buffer. until cx28500 relinquishes control, the data in this descriptor is being used by cx28500. 1 host owns buffer. cx28500 has relinquished control of buffer back to host. cx28500 is done processing buffer. 30 np no poll. copied from receive buffer descriptor. 29 eom 0 end of message indicator. the last by te for this message is not in this buffer. 1 end of message indicator. the last byte for this data message is in this buffer either because a valid closing flag (7eh) was detected or the receiver terminated due to an error condition. 28 eobien eob interrupt enabled. copi ed from receive buffer descriptor. 27:26 rsvd 0 reserved table 6-42. transmit buffer status descriptor (2 of 2) bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 117 mindspeed proprietary and confidential 6.8.8 data buffer pointer the data buffer pointer, defined in ta bl e 6 - 4 4 , is a 32-bit address to the first byte of a data message in shared memory. while operating in preserve channel mode (i.e., bit pc hmode in global configuration descriptor is set), cx28500 transfers in dataptr[1:0] the two msbs of the channel number and uses bit dataptr[2] to signal if this buffer is the first buffer of a received message (i.e., dataptr[2] is set) or not (i.e., dataptr[2] is clear). this is illustrated in ta bl e 6 - 4 5 . 25:18 rsvd/ chan [7.0] 0 when operating in normal mode (i.e., not in preser ve channel mode as indicated by bit pchmode in global configuration descriptor) this field is reserved. when operating in preserve channel mode (i.e., bit pch mode in global configurat ion descriptor is set0, this field is used by cx28500 to transfer in it the channel number least 8 significant bits. 17:15 error[2:0] 0 ok: no errors detected in this receive buffer. 1 buff: buffer error. data is lost due to internal data buffer overflow. 2 cofa: change of frame alignment. rsync signal is mi saligned with the flywheel in the serial interface. 3 oof: out of frame. roof signal is asserted. 4 abt: abort flag termination. r eceived message is terminated with abort sequence, seven sequential ones, instead of a closing flag (7eh). 5 lng: long message. message payload size greater than selected limit was received. message processing is terminated, and transfer to shared memory is discontinued. channel resumes scanning for hdlc flags or idle codes. 6 align: octet alignment error. message payload size, afte r zero extraction, is not multiple of 8 bits. this error takes precedence over a fcs error. 7 fcs: frame check sequence error. received hdlc frame is terminated with proper 7eh flag, but computed fcs does not match received fcs. 14 txlast ? last buffer indicator. copi ed from receive buffer descriptor. 13:0 dlen[13:0] ? number of received byt es stored by cx28500 in this buffer. general note: in eccmode, tx/rx buffer desc riptors are 64 bits in length. therefore, bot h the bsd and dataptr are written after the buffer is completely processed. note: while cx28500 does support byte addresses for the data, when operating in ecc mode, all rx and tx buffers must be 64-bit aligned. cx28500 assumes the three least significant bits of the data pointers are 0 regardless of the actual value. however, when updating the buffer desriptor status, cx28500 preserves the actual value. table 6-44. data buffer pointer bit field name value description 31:3 dataptr[31:3] ? this address points to the first byte of a data buffer. 2:0 don?t care ? table 6-43. receive buffer status descriptor bit field name value description
memory organization 28500-DSH-002-C mindspeed technologies ? 118 mindspeed proprietary and confidential table 6-45. data buffer pointer in pch mode bit field name value description 31:3 dataptr[31:3] ? write back dataptr value. 2 som_status 0 start of m essage status: not start. 1 start of message status: start of message contained in current buffer. 1:0 chan_msbs ? two most significant bits of the logical channel number chan[9:8].
28500-DSH-002-C mindspeed technologies ? 119 mindspeed proprietary and confidential 7.0 functional description 7.1 initialization 7.1.1 reset there is one level of reset: 1. hard pci reset 2. soft chip reset there are two ways to assert a reset: 1. assert the pci reset signal pin, prst*. 2. assert a service request through the host interface to perform the soft chip reset. after reset, the host needs to configure cx28500 for it to operate. this configuration includes several stages that should be performed in the following order:  pci configuration?needs to be performed only after hard pci reset  interrupt queue configuration  global configuration  channels and ports configuration 7.1.1.1 hard pci reset the pci reset is the most thorough level of reset in cx2850 0. all subsystems enter into their initial states, including the pci interface. pci reset is accomplished by asserting the pci signal, prst*. the prst* signal is an asynchronous signal on the pci bus. the reset signal can be activated in several ways. the system must always assert the reset signal on power-up. also, a host bus to pci bus bridging device should provide a way for software to assert the reset signal. additionally, software-controlled circuitry can be included in the system design to specifically assert the reset signal on demand. asserting prst* towards cx28500 guarantees that data tr ansfer operations and pci device operations do not commence until after cx28500 has been properly initialized for operation. upon entering pci reset state, cx28500 outputs a three-stated signal on all output pins and halt s activity on all subsystems including the host interface, serial interface, and expansion bus. note: the interrupt queue needs to be configured befo re other registers. if the interrupt queue is not configured with the corr ect value of shared memory interrupt queue pointer and interrupt queue length, it may result in writ es to location 0, since the service request acknowledge (sack) is written to a zero-address location.
functional description 28500-DSH-002-C mindspeed technologies ? 120 mindspeed proprietary and confidential the effects of a pci reset signal within cx28500 takes ten pci clock cycles to complete after deasserting the reset signal. after this time, the host can communic ate with cx28500 using the pci configuration cycles. after the pci configuration, the device is not ready to start communication with the host via service request mechanism until the srq_len bit field in service request register is set to 0. 7.1.1.2 soft chip reset a soft chip reset is a device-wide reset without the host interface?s pci state being reset. serial interface operations and ebus operations are halted. the soft chip reset state is entered in one of two ways:  as a result of the pci reset  as a result of a soft chip reset host service request a soft chip reset causes the following:  transmit data signals, tdat, to be three-stated  all ebus address lines to be three-stated and read enable and write enable outputs to be deasserted, halting all memory operations on ebus  all active channels to enter the channel deactivated state  dma controllers to be reset, halting all pci transactions  all registers reset to default values the host acts as if this was a pci reset, except that the pci configuration does not need to be repeated (it is kept unchanged). the host can assume that the reset was completed by cx28500 and can start configuration of registers when the field srq_len is zero. after any kind of reset, the user must reconfigure all aspects of cx28500. 7.1.2 configuration a sequence of hierarchical initialization must occur af ter resets. the levels of hierarchy are as follows:  pci configuration?only after hardware reset  interrupt queue configuration  global configuration  channel and port configuration channel and port configuration involves programming many registers and must be done to comply with its own hierarchy, as explained below. 7.1.2.1 pci configuration after power-up or a pci reset sequence, cx28500 enters a holding pattern. it waits for pci configuration cycles directed specifically for cx28500. they are actually dire cted at the pci bus and pci slot where cx28500 resides. pci configuration involves pci read and write cycles. these cycles are initiated by the host and performed by a host-bus-to-pci-bus bridge device. the cycles are executed at the hardware signal level by the bridge device. the bridge device polls all possible slots on the bus it controls for a pci device and then iteratively reads the configuration space for all supported functions on each device. all information from the basic configuration sequence is forwarded to the syst em controller or host processo r controlling the bridge device. during pci configuration, the host can perform the following configuration for cx28500:
functional description 28500-DSH-002-C mindspeed technologies ? 121 mindspeed proprietary and confidential  read pci configuration space (device identification, vendor identification, class code, and revision identification)  allocate 1 mb system memory range and assign the base address register using this memory range  allow fast back-to-back transactions  enable pci system error signal line, serr*  allow response for pci parity error detection  allow pci bus-master mode  allow pci bus-slave mode  assign latency  assign interrupt line routing 7.1.2.2 service request mechanism after pci configuration is complete, a set of hierarchical configuration sequences must be executed to begin operation at the channel level. the service request mechanism is the main communication channel between cx28500 and the host. it is used to configure cx28500?s registers, read status registers, execute transactions over the ebus, and activate ports and channels. the mechanism is fully described in section 6.2.1 . 7.1.2.3 global and ebus configuration global configuration is initiated by the host issuing service requests. global configuration specifies information used across the entire device including all ports, all channels, and the ebus. for more information, refer to:  section 6.4  section 6.5 7.1.2.4 interrupt qu eue configuration part of the global configuration involves interrupt queue configuration. for more information, refer to section 6.3.1 . 7.1.2.5 channel and port configuration after the global configuration, a specific channel and po rt configuration must be performed for each supported channel and port.  table 6-23, rslp channel configuration register  table 6-24, rdma buffer allocation register  table 6-25, rdma channel configuration register  table 6-26, rsiu time slot configuration descriptor  table 6-27, rsiu time slot pointer allocation register note: device identification at the pci configuration level must be used to identify the number of supported ports and channels in cx28500, whic h in turn affects cx28500?s configuration.
functional description 28500-DSH-002-C mindspeed technologies ? 122 mindspeed proprietary and confidential  table 6-28, rsiu port configuration register (the rx portalive register needs to be read and verified before writing to tsiu/rsiu port configuration register).  table 6-29, maximum message length register  table 6-31, tslp channel configuration register  table 6-32, tdma buffer allocation register  table 6-33, tdma channel configuration register  table 6-34, tsiu time slot configuration descriptor  table 6-35, tsiu time slot pointers register  table 6-36, tsiu port configuration register (the tx portalive register needs to be read and verified before writing to tsiu/rsiu port configuration register). notice that the order of configurations follows their internal addresses in cx28500. this enables the host to configure all of them using a single write command (config_wr) after setting the appropriate values in contiguous locations in its memory. for details see the section 6.2.1 . channel operations service request commands are:  ch_act: channel activate  ch_deact: channel de-activate  ch_jmp: channel jump 7.1.2.6 typical ini tialization procedure this section depicts a typical initialization procedure. 1. pci configuration 2. pci reset or soft chip reset (a soft chip reset is performed by a direct write to the cx28500 register map? in the soft chip reset register) 3. allocate areas in the share memory for:  interrupt queue  service request table  cx28500 configuration registers (global and local per channel/port/ts basis) 4. initialize values in allocated space for: xxxxxx 5. loop and wait for the service request length register to be ready. this step confirms that the cx28500 completed its intern al initialization. a. read the srq_len through the pci slave access and check if it is 0. b. if true, go to the next step. c. otherwise continue to check. 6. initialize the interrupt queue pointer register and interrupt length register by performing a direct write to the cx28500 registers with the address of the interrupt queue located in the shared memory and respectively its length. 7. check the port alive availability (i.e., txportalive and rxportalive) register by performing direct reads. for each active port the correspondent bit in txportalive and rxportalive registers needs to be set to 1. note: after performing a soft chip reset, it is not necessary to reconfigure the pci.
functional description 28500-DSH-002-C mindspeed technologies ? 123 mindspeed proprietary and confidential a. while port is not alive (this is equivalent with the correspondent bit not set) wait 8?16 serial line clocks. b. if port is not alive, poll until port is alive. c. otherwise go to the next step. 8. initialize the service request pointer (srp) and service request length (srl) registers by performing a direct write to the cx28500?s service request pointer and service request length register and update the value with the address all the srp table and its length in shared memory. 9. perform a config_wr service request and wait for the sack which copies the content of the register in shared memory in cx28500 internal register. the host can performe one config_wr service request given that all the registers have been initialized in the shared memory prior to the config_wr service request or can perform config_wr service request for each register individually. a detail typical configuration write request procedure is [13.1]. allocate the service request table in the shared memory. note: if the port is not alive in 16 line clocks then there are no serial clocks applied specific port. note: 1. this allocation can be done in the very beginning (see step 5 or in the configuration write request procedure) [13.2]. initialize the content of the service request table. [13.3]. initialize the service request po inter (srp) with the address of service request table by performing a direct write to the service request pointer register. [13.3] start the execution by writing the table length in to to the service request length register by performing a direct write. [13.4]. if other service request table is required, the host must poll the service request length register by performing a direct read and check the srq_len field. if this field is not 0, then cx28500 did not complete the execution of the last service request table. the number written in the srq_len indicates how many configuration wr ite commands (i.e., table entries) are pending for execution. while processing these commands, cx28500 generates sack interrupt for each command in which the sackien bit was set. when srq_len becomes 0, the host can start from [13. 1], whereas prior to a new execution either frees the memory which was allocated for the prior service request table or uses the same memory as a pool memory. the regist ers which are initialized through service request mechanism are as follows: 2. global configuration [1] (one per chip) 3. rslp channel configuration [1024] (for each channel to be activated) 4. rdma buffer allocation [1024] (for each channel to be activated) 5. rdma configuration [1024] (for each channel to be activated) 6. rsiu time slot configuration [4096] (for each time slot to be used) 7. rsiu time slot pointer [32] (for each port to be activated) 8. rsiu port configuration [32] (for each port which should operate, this command activates the port) 9. rslp max. message length [3] (three registers) 10. receive base address head pointer [1] (one per chip) 11. transmit base address head pointer [1] (one per chip) 12. ebus configuration [1] (one per chip) 13. tslp channel configuration [1024] (for each channel to be activated) 14. tdma buffer allocation [1024] (f or each channel to be activated) 15. tdma configuration [1024] (for each channel to be activated) 16. tsiu time slot configuration [4096] (for each time slot to be used) 17. tsiu time slot pointer [32] (for each port to be activated) 18. tsiu port configuration [32](for each port which should operate, this command activates the port)
functional description 28500-DSH-002-C mindspeed technologies ? 124 mindspeed proprietary and confidential 7.2 channel operations 7.2.1 channel activation channel activation is an asynchronous command from the host interface to a transmit or receive section of a channel to jump to a new message. message descriptors in shared memory describe the attributes of the new message, what to do between messages, and identify the location of message data buffers in memory to use for transmit data or receive data. after the previous levels of configuration are completed, individual channels are ready to be activated. service requests are used to activate channels. each channel consists of a transmitter and a receiver section. each section is independent of the other and maintains its own state machine, configuration registers, and internal resources. to activate both transmitter and receiver sections, two separate service requests are required, one directed to the transmitter and one to the receiver. cx28500 responds to each service request with the sack interrupt descriptor, which notifies the host that the task was initiated. the notification to the host that the task was completed is an eoce interrupt. this acknowledges the host that the srq was completed. upon channel activation, cx28500 flushes out all internal fifo?s, slp?s, and dma?s, then, updates their head pointer tables. 7.2.1.1 transmit channel activation the following describes what cx28500 does when the transmit channel is activated. 1. cx28500 reads tx head pointer for channel from shared memory and stores it in the internal channel descriptor map, and generates an eoce interrupt if it?s enabled. 2. cx28500 reads message descriptor (buffer descriptor and data pointer) pointed to by the fetched tx head pointer and stores it in internal channel descriptor memory. the actual read of the message descriptor depends on crossing a threshold in the internal transmit fifo. in this case, however, because the activation command empties the internal transmit fifo, which causes it to cross the fifo threshold, it is guaranteed that the message descriptor is read. 3. cx28500 checks bit field owner and np in buffer descriptor. if owner = 1, cx28500 is buffer owner. go to step 4. if owner = 0, cx28500 is not the buffer owner and tdma buffer processing for this channel is temporarily suspended. there are several ways of tdma to exit the channel suspended state: a. channel is instructed to jump to a new md list (see ch-jump). b. channel is instructed to reactivate to a new md list, go to step 1. c. while np is zero, tdma polls curren t bd until owner = 0, go to step 4. note: the steps [1] to [17] can be performed in one single step by setti ng the service request table with two entries and waiting for only one sack or eci. this increases the performance over the pci bus. 19. perform a ch_act service request and wait for sack when the sackien bit is set. for each channel that needs to be activat ed, the host prepares a ch_act service request and inserts it into the service requ est table. the host m ay decide to activate all channels by writing the service request queries into one single service request table or by splitting the service request co mmands into one or more tables. for each ch_act service request the host follows th e same steps as were specified at [13.1] through [13.4]
functional description 28500-DSH-002-C mindspeed technologies ? 125 mindspeed proprietary and confidential d. if np is 1, then tdma does not poll the current bd, and this channel remains suspended until one of conditions a. through b. are satisfied. if cx28500 is in the middle of transmitting a message and the np bit becomes 1, the tdma generates a txonr interrupt (if onreim is unmasked). 4. cx28500 reads data from the memory buffer to internal fifo until either an end of message (eom) is fetched or the entire memory buffer (blen) is read. this is not true for transmission. in the transmit direction, cx28500 reads all valid data buffers regardless of eom. 5. cx28500 transmits the read data as an hdlc frame, or as a transparent frame depending on the type of protocol selected for the channel. 6. cx28500 checks inhtbsd bit field: if inhtbsd = 0, cx28500 overwrites the buffer descriptor (bd) with a buffer status descriptor (bsd) file, do not write buffer status descriptor (bsd). if the buffer contains an eom, the tslp posts a txeom interrupt (if eomiem unmasked). 7. cx28500 checks last bit field:  if last = 0, cx28500 advances the current md pointer.  if last = 1, cx28500 sets current md pointer equal to head pointer. 8. cx28500 reads the next message descriptor. go to step 3. 7.2.1.2 receive channel activation the following describes what cx28500 does when receive channel is activated. 1. all internal fifos are flushed cx28500 reads rx head pointer for channel from shared memory and stores it in internal channel descriptor map. 2. simultaneously, the receiver is configured and data is sampled in from serial port using control lines. cx28500 does not pass the control to the host memory (i.e., it does not move to step 3) until enough data is accumulated in its internal buffers (i.e., the threshold programmed for this channel gets crossed). if hdlc mode is selected, the rsiu will scan for an opening flag. 3. cx28500 reads message descriptor (receive buffer descriptor and data pointer) pointed to by the fetched rx head pointer and stores in internal channel descriptor memory. 4. cx28500 checks bit field owner and np in receive buffer descriptor. if owner = 0, cx28500 is the buffer owner, go to step 5. if owner = 1, cx28500 is not the buffer owner and rdma buffer processing for this channel is temporarily suspended. there are several ways for rdma to exit the channel suspend state: a. channel is instructed to jump to a new md list (see channel jump). b. channel is instructed to reactivate to a new md list, go to step 1. c. while np is 0, rdma polls current bd until owner = 0, go to step 5. d. if np is 1, then rdma does not poll the current bd, and this channel goes to suspended until one of conditions a through b are satisfied). if cx28500 is in the middle of receiving a message and the np bit becomes 1, the rdma generates a rxon r interrupt (if onrien is unmasked). note: because transmit eob and eom interrupts are i ndependent events if the buffer contains an eom, two interrupts are generated, an eob interr upt when the last data byte is read into internal memory, and an eom interrupt when th e last data byte is transferred from the internal memory to the serial interface unit. if the buffer is not eom, cx28500 posts a txeob interrupt (if eobien is set).
functional description 28500-DSH-002-C mindspeed technologies ? 126 mindspeed proprietary and confidential 5. cx28500 writes data from its fifo to the memory buffer until either an end of message (eom) is stored or the entire memory buffer (blen) is filled. 6. cx28500 checks inhtbsd bit field in section 6.6.4 . if inhtbsd = 0 (i.e., cx28500 is allowed to overwrite buffer descriptor with a buffer status descriptor), it overwrites the receive buffer descriptor. if the message ended (i.e., eom is set in the receive buffer status descriptor), go to step 7. if the eom is not set in receive buffer status, it might generate an eob interrupt depending on eobien bit setting in the receive buffer descriptor. go to step 8. 7. if the receive buffer descriptor contains the end of message (eom), an interrupt descriptor is written in the shared memory depending on the mask interrupt status. 8. depending on the last bit value set in the receive buffer descriptor, cx28500 reads the next message descriptor. go to step 4. 7.2.2 channel deactivation a channel deactivation is an asynchronous command from the host interface to a transmit or receive section of a channel to suspend processing and halt memory transfers into shared memory. after the channel has been activated, channel deactivation via a service request suspends activity on an individual channel direction. each channel consists of a transmitter and a receiver section. each section is independent of the other and maintains its own state machine and configuration registers. to deactivate both transmitter and receiver sections, two separate service requests are required, one directed to the transmitter and one to the receiver. cx28500 may respond to each service request with the sack interrupt descriptor, which notifies the host that the task was initiated. the notification to the host that the task was completed is an eoce interrupt. this acknowledges the host that the srq was completed. 7.2.2.1 transmit channel deactivation the following describes what cx28500 does when transmit channel is deactivated: 1. current message processing is terminated destructively. that is, data can be lost and messages prematurely aborted. cx28500 does not give any indication of a lost message. if a message descriptor is in the middle of processing, it is left as it is. 2. internal fifos are flushed and the data is lost. 3. the tslp is responsible for handling outbound bits when the serial port is asynchronously disabled. the data output pin, tdat, is held at logic 1. data transfers from shared memory are halted. 4. the transmit channel remains in the suspended state until the channel is activated. the current channel direction configuration is maintained. 7.2.2.2 receive channel deactivation the following describes what cx28500 does when receive channel is deactivated: 1. current message processing is terminated destructively. that is, data can be lost and messages prematurely aborted. cx28500 gives no indication of the lost messages. if a message descriptor is in the middle of processing, it is left as it is. 2. internal fifos are flushed, and all data is lost. 3. the rslp is responsible for handling inbound bits when the serial port is asynchronously disabled. data transfers to shared memory are halted.
functional description 28500-DSH-002-C mindspeed technologies ? 127 mindspeed proprietary and confidential 4. the receive channel remains in the suspended state until the channel is activated. the current channel direction configuration is maintained. 7.2.3 channel jump a jump request is issued by the host via a service request (ch_jmp). notice that the jump service request acknowledge (via the sack interrupt descriptor) is output toward the host immediately. the eoce interrupt acknowledges that the ch_jmp service request was performed, and the next head pointer was read. however, this does not mean that cx28500 starts working on the new message descriptors table pointed by the new head pointer immediately. channel jump takes effect after an end of message (eom) is fetched from or stored to memory buffer or while the channel is in suspended state. 7.2.3.1 receive channel jump for a receiver, channel jumps do not affect the current message being transferred to the host (if there is such a message). the command is executed only after the current message transfer to the host is completed. no internal fifo flushing happens; the next messages are transferred using the new message descriptors provided by the jump command. the channel state is not reset as in the channel activate sequence. for a receiver, channel jumps provide a non-destructive way of storing incoming data using a new message descriptors table. 7.2.3.2 transmit channel jump for a transmitter, channel jumps are non-destructive to currently serviced messages. the channel state is not reset as in the channel activate sequence. hence, a transmitter channel must be activated first, then subsequent jump requests can be made using the channel jump service request. for a transmitter, channel jumps provide a nondestructive way to start transmitting the new message list. cx28500 waits until the completion of the current message before jumping to the new message array pointed to by a new head pointer. 7.2.4 channel reactivation a channel reactivation happens when an activate command is issued to an active channel. cx28500 behavior is as if the channel was deactivated and then activated again. this means that the sequence described in section 7.2.2 happens followed by the sequence described in section 7.2.1 . however, only one sack interrupt and one eoce interrupt are generated. sack is generated to indicate the initiation of the operation, and eoce is generated to indicate the completion of channel reactivation. 7.2.5 unmapped time slots the host can stop cx28500 from processing certain time slots regardless of the channel activation/deactivation/ jump/reactivation commands. this can be performed by programming time slots in rsiu time slot configuration and tsiu time slot configuration to indicate th at the specific time slots are not mapped (see rts_enable and tts_enable bit fields in table 6-26, rsiu time slot configuration descriptor and ta b l e 6 - 3 4 , tsiu time slot configuration descriptor , respectively). note: the tdat signal is either set to logic 1 or three-state according to bit tritx in section 6.7.5 .
28500-DSH-002-C mindspeed technologies ? 128 mindspeed proprietary and confidential 8.0 basic operations the two main channel protocols, hdlc and transparent mode, are described in subsequent sections of this chapter. hdlc and transparent mode operations perform pr otocol-specific processing of their respective input and output serial bit streams and behave differently in their treatment of those bit streams during abnormal conditions. 8.1 protocol-independent operations from a functional viewpoint, many cx28500 operations are protocol-independent, though some behaviors may differ between the transmitter and receiver. the protocol-independent operations described below apply to all event and error handling:  during dma shared memory, slp channel protocol and siu serial port operations, an event or error may occur that indicates the status of the message transfer process or that affects the outcome of the overall message transfer process. unless masked, all such events and errors cause cx28500 to write an interrupt descriptor to the shared memory interrupt queue. interrupt descriptors identify the error or event condition, the transmit or receive direction, and the affected channel or port number.  if cx28500 suspends a channel?s operation, the host must perform a channel reactivation by issuing either a channel activation service request or a channel jump service request. this is referred to as ?requiring reactivation.? on the receiving side one scenario that would suspend a channel is when a message descriptor is host owned and np = 1 is encount ered. on the transmission side, seve ral occurrences of cofa?s will cause the tslp to stop transmission, hence suspending all active channels.  if cx28500 deactivates a channel, the host must perform a channel reactivation by issuing a channel activation service request. th is is referred to as ?requiring complete reactivation.?  the bit fields inhtbsd and inhrbsd in the rdma/td ma channel configuration registers specify whether cx28500 writes a buffer status descriptor into t he message descriptor to indicate that cx28500 has completed servicing both the message descriptor and its associated data buffer.  during the normal course of shared memory buffer pr ocessing, the dma calculates the position of the next message descriptor within the message descriptor table and reads that buffer descriptor to determine ownership. the buffer descriptor?s onr bit field indica tes whether cx28500 or the host owns that particular message descriptor and its associated data buffer. cx28500 never writes to a host-owned descriptor nor processes its associ ated data buffer.  whenever both eob and eom events happen together, an eom interrupt is generated and an eob interrupt is not generated for the receive direction. that is, unless the eom interrupt is disabled (masked) and the eob interrupt is enabled (unmasked), in which case an eob inte rrupt is generated. this is true even if the cause of the eom interrupt was due to an error condition. for the transmit direction, since eob and eom are independent, both interrupts will be reported if they are enabled.
basic operations 28500-DSH-002-C mindspeed technologies ? 129 mindspeed proprietary and confidential 8.1.1 transmit cx28500 initiates data transfer to the serial interface only if the following conditions are true:  txenbl bit set to 1 in ta bl e 6 - 3 6 , tsiu port configuration register .  transmit channel is mapped to time slots, which are enabled in the port?s section 6.7.5 .  transmit channel has been activated by a host service request.  if not in unchannelized mode, then cx28500 waits until the first detection of a sync pulse or strobe to get out of three-state. if txenbl bit is set to 0 (transmit port disabled), the se rial data output signal is placed in high-impedance three- state. if txenbl = 1 (port enabled) and a time slot is disa bled, the corresponding time slot?s transmitter output is either a three-state or all 1s depending on the state of the tritx bit field in the port?s ta bl e 6 - 3 6 , tsiu port configuration register . 8.1.2 receive the receiver processes data from the serial interface only if all of the following conditions are true:  rxenbl bit is set to 1 in the port?s ta b l e 6 - 2 8 , rsiu port configuration register .  receive channel is mapped to time slot(s), that are enabled in the port?s section 6.6.5 .  receive channel has been activated by a host via service request. if any one of the above conditions is not true, the receiver ignores the incoming data stream. data transfer consists of cx28500 first seeking the (next) message descriptor from the message descriptor in shared memory for each active channel. the buffer descriptor in each message descriptor, plus the protocol mode set for the channel, dictates the treatment of the incoming bit stream. 8.2 hdlc mode cx28500 supports three hdlc modes. the modes are assigned on a per-channel and direction basis by setting the protocol bit field within the rslp/tslp channel configuration registers. the hdlc modes are as follows:  hdlc_nocrc: hdlc support, no crc  hdlc-16crc: hdlc support, 16-bit crc  hdlc-32crc: hdlc support, 32-bit crc hdlc protocol-specific support in th e transmitter includes the following:  generate opening/closing/shared flags  zero bit insertion after five consecutive 1s are transmitted  generate pad fill between frames and adjust for zero insertions  generate 0-, 16- or 32-bit crc (i.e., fcs)  generate abort sequences upon fifo underflow condition or as instructed on a per-message basis by the abort field in the message descriptor note: if txenbl = 1 and the port is configured in any channelized mode (i.e., not unchannelized), until the first tsync/stb pulse is detected , that port outputs either a three-state signal or all 1s depending on the state of the tritx bit field.
basic operations 28500-DSH-002-C mindspeed technologies ? 130 mindspeed proprietary and confidential  data polarity inversion of all bits (including flags and padfill characters) hdlc protocol-specific support in the receiver includes the following:  detection and extraction of opening/closing/shared flags  detection of shared-0 between successive flags  zero bit extraction after five consecutive 1s are received  detect changes in pad fill idle codes  check and extract 0-, 16- or 32-bit fcs  check frame length  check for octet alignment. failures result in eom and an error code in the buffer/interrupt descriptor  check for abort sequence reception  after channel activation, check for the first flag character to be received and generate a chic interrupt the transmit buffer descriptor specifies inter-message bit- level operations. specifically, when the eom bit field is set to 1 within a message descriptor by the host, it signifies that the descriptor represents the last buffer for the current message being transmitted and the bit fields ic and padcnt take ef fect. these bits are described in section 8.2.5 . additionally, the np bit field in both receive and transmit buffer descriptors selects whether cx28500 polls a host-owned message descriptor. 8.2.1 frame check sequence cx28500 is configurable to calculate and insert either a 16- or 32-bit frame check sequence (fcs) for hdlc packets, provided the packet length contains a minimum of 2 octets. the fcs is always calculated over the entire packet length. for all hdlc modes that require fcs calculation, the polynomials used to calculate fcs are according to itu-t q.921 and iso 3309-1984.  crc-16  crc-32 8.2.2 opening/closing flags for hdlc modes only, cx28500 supports the use of op ening and closing message flags. the 7eh (01111110b) flag is the opening and closing flag. an hdlc message is always bounded by this flag at the beginning and the end of the message. cx28500 supports receiving a shared flag where the closing flag of one message can act as the opening of the next message. cx28500 also supports receiving a shared-zero bit between two flags?that is, the last zero bit of one flag is used as the first zero bit of the next flag. receiving a shared zero between the fcs and the closing flag is not supported. cx28500 can be configured to transmit a shared flag between successive messages by configuring the bit field padcnt in each transmit buffer descriptor. cx28500 does not transmit shared-zero bits between successive flags. x 16 x 12 x 5 1 +++ x 32 x 26 x 23 x 22 x 16 x 12 x 11 x 10 x 8 x 7 x 5 x 4 x 2 ++++++++++++ x 1 ++
basic operations 28500-DSH-002-C mindspeed technologies ? 131 mindspeed proprietary and confidential 8.2.3 abort codes at least seven consecutive 1s constitute an abort code . receiving the abort code causes the current frame processing to be aborted, and further data transfer into shared memory for that message is terminated. after detecting the abort code, cx28500 enters a scan mode, which searches for a new opening flag character. notification of this detected condition is provided by the receive buffer status descriptor and/or an interrupt descriptor indicating the error condition abort flag termination. in cases where received idle codes transition to an abort code, an interrupt descriptor is generated toward the host (if enabled in section 6.6.2 ), indicating the informational event change to abort code. all received abort codes are discarded. in the transmission direction, an abort code?s handling is depended on what the user tells cx28500 to do. an abort code could just abort the transmission of the current message, or it can mean aborting the current message transmission and then starting transmitting the next message, if it exists. 8.2.4 zero-bit insertion/deletion cx28500 provides zero-bit insertion and deletion when it encounters five consecutive 1s within a frame. in the receiver, the zero bit is removed (discarded). in the transmitter, the zero bit is inserted after each sequence of five ones. zero-bit insertion, or bit-stuf fing, is only done in the message se ction and not in th e pad fill section. 8.2.5 message configur ation bits?hdlc mode the transmit buffer descriptor contains message configurati on bits to specify what data pattern is transmitted after the end of a current message and its respective closing fl ag have been transmitted. the bits are specified as follows:  idle code specification, ic  inter-message pad fill count, padcnt  send an abort sequence, abort 8.2.5.1 idle code the idle code (ic) specification allows one of a set of idle codes to be chosen to be transmitted after the current message in case the next message is not available to be transmitted or in ter-message pad fill is requested via padcnt. the default idle code for hdlc mode is flag, or 7eh. 8.2.5.2 inter-message pad fill the pad count (padcnt) specification allo ws pad fill octets (a sequence of one or more specified idle codes) to be transmitted between messages. pad cnt is the minimum number of fill oc tets to be transmitt ed between closing flag of one message and the opening flag of the next message in the following manner: note: seven ones are the abort condition cx28500 checks for while receiving a message, but the criteria for detection and gene ration of a change to abort code interrupt is equal to 14 consecutive ones. note: message configuration bits are also used in transparent mode with slightly different meanings. for details see section 8.3.1 .
basic operations 28500-DSH-002-C mindspeed technologies ? 132 mindspeed proprietary and confidential 1. padcnt = 0: shared open/close flag 2. padcnt = 1: separate open/close flags, no idle code 3. padcnt = 2: separate open/close flags, at least one idle code this pad fill feature enables rate adapta tion applications (i.e., isdn rate adap tation), as defined in itu standards v.110 and v.120. furthermore, cx28500 al so allows the reduction of the numb er of pad fill octets to compensate for the number of zero-bit insertion. one pad fill octet is omitted from tr ansmission for every eight zero-bit insertions. the number of zero-bit inse rtions is rounded up to t he nearest number of octets for pa d fill adjustment. pad count adjustment can be enabled in the tlsp channel configuration register. for details, please see section 6.7.2 8.2.5.3 ending a message with an abort or sending an abort sequence if blen = 0 in any transmit buffer descriptor, cx28500 interprets it as a request to end an in-progress message with the abort sequence. if the previous buffer descriptor (before the blen = 0 buffer) contained an end-of- message (eom) indication, the abort request is simply ignored and cx28500 moves on to the next message descriptor. if the previous buffer descriptor was not eom (i.e., a transmit message was in-progress), an abort code sequence is transmitted to end that partially sent message. transmission of an abort code sequence is defined as 16 consecutive 1s. 8.2.6 transmit events transmit events are informational in nature and do not require channel recovery actions. 8.2.6.1 end of buffer [eob] reason:  tdma reached the end of a shared memory buffer by servicing the number of bytes equal to blen in the transmit buffer descriptor. note that transmit eob and transmit eom events are not coincident in time, so they result in two separate events being generated. effects:  txeob interrupt (if eobien = 1 in transmit buffer descriptor).  cx28500 continues with normal message processing . if the tdma does not get more data from shared memory before the tslp needs to output the next data bit (assuming the message did not end), the tslp enters underflow state, described below. 8.2.6.2 end of message [eom] reason:  tslp has transmitted (actually, transferred to the tsiu) the last bit of a data buffer (excluding the fcs and closing flag) and the transmit buffer descriptor signifie s that buffer contained an end of a message (eom = 1). effects:  txeom interrupt (if eomien = 1 in section 6.7.2 ). note: eob and eom are not coincident, resulting in separate events.
basic operations 28500-DSH-002-C mindspeed technologies ? 133 mindspeed proprietary and confidential  tslp and tdma continue normal processing. if the td ma does not get more data from shared memory before the tslp needs to output the next data bit, tslp outputs another octet of flag or idle code. 8.2.6.3 abort termination reasons:  the user wants to abort the transmission of the current message. for details, please see section 6.8.6 .  to provide a mechanism for the self-served transmitter to recover from a receiver error. for details, please see chapter 9.0 . effects:  cx28500 stops transmitting the current message, sends out an abort sequence, and goes on to process the next message, if it exists. 8.2.7 receive events receive events are informational in nature and do not require channel recovery actions. 8.2.7.1 end of buffer [eob] reason:  one message is split across multiple shared memory buffers. cx28500 reached the end of a buffer by servicing (writing) the number of bytes equal to blen specified in the receive buffer descriptor. effects:  eob interrupt (if eobien = 1 in receive buffer descriptor).  rdma and rslp continue normal processing. 8.2.7.2 end of message (eom) reason:  rslp has detected the end of a message (closing flag or an error condition). error conditions include: overflow, cofa, oof, abort, too long, alignment, and fcs error. effects:  if there were no errors, rxeom interrupt (if eomien = 1 in section 6.6.5 ). if there were errors, rxeom interrupt (if errien = 1 in section 6.6.4 and section 6.7.4 )  rdma sets eom = 1 in receiv e buffer status descriptor (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ).  rdma and rslp continue normal processing. 8.2.7.3 change to abort code (chabt) reason:  rslp detected received data changed from flag (7eh) octets to abort code (zero followed by fourteen consecutive ones) in the idle code section of the bit stream and not in the message payload section. an abort code detection in the message payload results in an abort termination error.
basic operations 28500-DSH-002-C mindspeed technologies ? 134 mindspeed proprietary and confidential effects:  chabt interrupt (if idleien = 1 in section 6.6.2 ).  rslp and rdma continue normal processing. 8.2.7.4 change to idle code (chic) reason:  rslp detects received data changed to flag (7eh) octets. cx28500 requires detection of three consecutive flags and the previous idle code is all 1s before a chic event is generated. effects:  chic interrupt (if idleien = 1 in section 6.6.2 ).  rslp and rdma continue normal processing. 8.2.7.5 frame recovery (frec) or g eneric serial port (sport) interrupt reason:  rsiu detects the serial interface roof signal transition from an out-of-frame (roof = 1) to an in-frame (roof = 0) condition. if the roof signal is programmed for use as an out-of-frame indicator, this frame recovery event (roof returning low) generates a frec interrupt after one full frame without roof assertion. if the roof signal is used as a general-purpose interrupt input, this event generates a sport (serial port) interrupt. since both frec and sport interrupt even ts are reported in the same field in the non-dma interrupt descriptor, the user must interpret the event according to how the roof signal is used. effects:  frec/sport interrupt (if oofien = 1 in ta bl e 6 - 2 8 , rsiu port configuration register ).  rslp and rdma continue normal processing. 8.2.7.6 receive cofa recovery (rcrec) reason:  rsiu terminates the internal cofa condition due to the arrival of a rsync/tstb pulse followed by at least the assigned number of time slots for this po rt without another unexpected rsync/tstb pulse. effects:  rcrec interrupt (if cofaien = 1 in ta bl e 6 - 2 8 , rsiu port configuration register ).  rslp and rdma continue normal processing. 8.2.8 transmit errors transmit errors are service-affecting an d require a corrective action by a c ontrolling device (i.e., the host) to resume normal channel processing. note: after channel activation/reactivat ion, the first flags detected on the line generate a chic interrupt.
basic operations 28500-DSH-002-C mindspeed technologies ? 135 mindspeed proprietary and confidential 8.2.8.1 transmit underrun [buff] cx28500 needs to send more data toward the tsiu for an in-progress transmit message, but the internal channel fifo is empty. reasons:  degradation of the host subsystem or application software.  buffer descriptor containing the continuation of a message is host-owned.  pci bus congestion. effects:  txbuff interrupt (if buffien = 1 in section 6.7.2 ).  transmit channel enters deactivate state where the tslp transmits a repetitive abort sequence of 16 consecutive 1s.  tdma may read more buffers to refill the internal channel fifo (since th is process is asynchronous to the tslp), but eventually the tdma stops servicing this channel since the tslp has stopped sending data.  transmit output is all 1s, or an abort code, to indicate a termination event. channel level recovery actions:  transmit channel complete reactivation is required. 8.2.8.2 transmit change of frame alignment (cofa) the tsync or stb input signal transitions from low to high, but at an unexpected time in comparison to the internal frame synchronization flywheel mechanism. cofa errors are only applicable to channelized ports (i.e., unchannelized ports ignore the tsync input). frame synchronization indicates the expected location of the first bit of time slot 0 on the transmit serial data output. lacking frame synchronization, the transmitter cannot map or align time slots. this error affects all active channels on the respective port. reason:  signal failure, glitch or realignment caused by the physical interface sourcing the tsync/stb input signal. effects:  causes serial interface to enter cofa condition until a tsync/stb pulse arrives and is followed by at least the assigned number of time slots for this port, without another unexpected tsync/stb pulse.  for every active channel on the respective port, tslp places channels into the deactivate state. wherein, tslp sends a repetitive abort sequence of 16 consecutive ones.  transmit cofa interrupt (if cofaien = 1 in section 6.7.5 ). note: since cx28500 completely separates the two processes of loading data from the host and transmitting data to the serial interface, it is irrelevant to cx28500 how the underrun condition was created. to be specific, there is no distinction between a buff error created due to a host-owned buffer descriptor or du e to a latency-induced empty fifo condition. cx28500 behavior when encountering a buffer descriptor owned by the host is described in table 6-40, transmit buffer descriptor . the behavior is the same regardless of the presence or absence of an underrun condition. the effects of an underrun condition, once detected, are as described above, rega rdless of current buffer ownership. note: cofa interrupt is generated immediately. to synchronize the host?s response to a cofa condition, a cofa recovery interrupt is also provided.
basic operations 28500-DSH-002-C mindspeed technologies ? 136 mindspeed proprietary and confidential  tdma can read more buffers to refill the internal cha nnel fifo (since this proc ess is asynchronous to the tslp), but eventually the tdma stops servicing this channel since the tslp has stopped sending data.  transmit output is three-stated. channel level recovery action:  transmit channel complete reactivation is required. 8.2.8.3 transmit cofa recovery (tcrec) reason:  tsiu terminates the internal cofa condition due to the arrival of a tsync/stb pulse followed by at least one frame for this port without another unexpected tsync/stb pulse. effects:  tcrec interrupt (if cofaien = 1 in ta b l e 6 - 3 6 , tsiu port configuration register ). channel level recovery actions:  transmit channel complete reactivation is required. must wait until cofa recovery interrupt is generated, then reactivate the channel. if the cofa event is not flushed via a channel reactivation, then the port is three-stated, again. 8.2.9 receive errors receive errors are service-affecting, but do not require a corrective action by the host to resume normal processing, except when cx28500 fetches a host owned np = 1 message buffer descriptor. then a jump service request is required to resume normal processing. 8.2.9.1 receive overflow [buff] the rxdma receives a signal from the rslp that more data bits are available to be stored, but the rxdma channel fifo is already full. reasons:  degradation of host subsystem performance.  shortage of shared memory buffers. the receive bu ffer cx28500 needs to fill is presently host-owned.  pci bus congestion. effects:  rxbuff interrupt (if buffien = 1 in section 6.6.2 ).  if a receive message was in-progress, that message is marked as errored. rslp scans for the opening flag of the next hdlc message and any subsequent receive messages are discarded until the internal fifo has room to accept more rsiu data. notice the channel remains active, and channel recovery is automatic. note: in all the cases where a message is received and its buffer descriptor is closed with any of the errors listed below, the abort field of th e receive status descriptor is set to non-zero. this ensures a transmitter operating in the self-servicing buffer mode (see below) ends each incomplete message with an appropriate abort code.
basic operations 28500-DSH-002-C mindspeed technologies ? 137 mindspeed proprietary and confidential  when the in-progress message reaches the top of the internal fifo, the entire hdlc message (before the overflow occurred) is copied to shared memory buffers and their last receive buffer status descriptors are written with onr = host, eom = 1, error = buff (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ).  rxerr interrupt is generate d, if errien is set in section 6.6.4 and section 6.7.4 , indicating a rxbuff error overflow.  rdma is not affected and continues shared memory buffer processing.  if a consecutive overflow condition exists, only the fi rst overflow triggers an overflow interrupt while all succeeding overflows are discarded and not reported. channel level recovery actions:  if possible, increase internal fifo size assigned to this channel. for this action, the channel must first be deactivated.  if necessary, alleviate pci bus congestion.  notice that channel reactivation is not required. 8.2.9.2 receive change of frame alignment (cofa) rsync or stb input signal transitions from low to high, but at an unexpected time in comparison to the frame synchronization flywheel mechanism. co fa errors are only applicable to channelized ports (i.e., unchannelized ports ignore the rsync/stb input). frame synchronization in dicates the expected location of the first bit of time slot 0 on the receive serial data input. lacking frame synchronization, the receiver cannot map or align time slots. this error affects all active channels on the respective port, but does not require a host recovery action. reason:  signal failure, glitch, or realignment caused by the phys ical interface sourcing the rsync or stb input signal. effects:  causes serial interface to enter cofa condition un til the rsync/stb pulse is followed by at least the assigned number of time slots for this port, without another unexpected rsync/stb pulse.  if a receive message was in-progress, that message is marked as errored. rslp scans for the opening flag of the next hdlc message and any subsequent receive messages are discarded until the internal cofa condition has ended.  when the in-progress message reaches the top of the internal fifo, the entire hdlc message is copied to shared memory buffers, and receive buffer status descriptors are written with onr = host and error = cofa (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ).  receive cofa interrupt is generated (if cofaien = 1 in ta b l e 6 - 2 8 , rsiu port configuration register ). note that a tstb change of alignment causes both a receive and a transmit cofa interrupt, since tstb applies to both transmit and receive directions simultaneously.  normal operations continue after the cofa condition ends.  rdma is not affected and continues shared memory buffer processing. note: since cx28500 completely separates the two processes of storing data in shared memory buffers and receiving data from the serial inte rface, it is irrelevant to cx28500 how the overflow condition was created. to be specific, there is no di stinction between a buff error created due to a host-owned buffer descriptor or due to a latency-induced full fifo condition. cx28500 behavior when encountering a buffer descriptor owned by the host is described in table 6-41, receive buffer descriptor . the behavior is the same regardless of the presence or absence of an overflow conditi on. the effects of an overflow condition, once detected, are as described above, re gardless of the current buffer ownership.
basic operations 28500-DSH-002-C mindspeed technologies ? 138 mindspeed proprietary and confidential channel level recovery actions:  none required. 8.2.9.3 out of frame (oof) out-of-frame or loss-of-frame indicates the entire, or partial, receive serial data stream is invalid and only time slots marked with oof from that port should be ignored. reason:  roof input pin is asserted (high) because the attached physical layer device is unable to recover a valid, framed signal. effects:  oof interrupt (if oofien = 1 and oofabt = 1 in ta bl e 6 - 2 8 , rsiu port configuration register ).  if bit field oofabt = 0, rslp and rdma continue as if no errors and transfer received data into shared memory buffers normally.  if bit field oofabt = 1 and a receive message is in-progress, the current message is ended with oof status and rslp scans for the opening flag of the next hdlc message. when the in-progress message reaches the top of the internal fifo, the entire message is copied to shared memory buffers and the buffer status descriptor is writte n (if inhrbsd = 0 in section 6.6.5 ) with onr = host and error = oof.  rdma is not affected and continues shared memory buffer processing.  receive channels recover automatically when the roof input pin is deasserted (low), indicating the oof condition has ended. channel level recovery actions:  none required. 8.2.9.4 frame check sequence (fcs) error in this case, the frame check sequence (fcs) which cx28500 calculated for the received hdlc message does not match the fcs located within the message. reason:  bit errors during transmission. effects:  when the message reaches the top of the internal fifo, the entire hdlc message is copied to shared memory buffers and the buffer status descriptor is written (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ) with onr = host, error = fcs.  eom interrupt with rxfcs error status, (if errien = 1 in section 6.6.4 and section 6.7.4 ).  the rslp scans for the opening flag of the next hdlc message.  rdma is not affected and continues shared memory buffer processing. channel level recovery actions:  none required.
basic operations 28500-DSH-002-C mindspeed technologies ? 139 mindspeed proprietary and confidential 8.2.9.5 octet alignment error (align) the hdlc message size after zero-bit extraction was not a multiple of 8 bits. reasons:  bit errors during transmission.  incorrect message transmission from distant end. effects:  when the message reaches the top of the internal fifo, the entire hdlc message is copied to shared memory buffers and the buffer status descriptor is written (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ) with onr = host, error = align.  eom interrupt with rxalign error status, (if errien = 1 in section 6.6.4 and section 6.7.4 ).  the rslp scans for the opening flag of the next hdlc message.  rdma is not affected and continues shared memory buffer processing. channel level recovery actions:  none required. 8.2.9.6 abort termination (abt) the receiver detects an abort sequence in the middle of the message payload. an abort sequence is defined as any zero followed by 15 consecutive 1s. reasons:  distant end failed to complete transmission of the hdlc message.  path conditioning has replaced the normal channel content with an all ones pattern, due to a network alarm condition. effects:  when the message reaches the top of the internal fifo, the entire hdlc message is copied to shared memory buffers and the buffer status descriptor is written (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ) with onr = host, error = abt.  eom interrupt with rxabt error status, (if errien = 1 in section 6.6.4 and section 6.7.4 ).  the rslp scans for the opening flag of the next hdlc message.  rdma is not affected and continues shared memory buffer processing. channel level recovery actions:  none required. 8.2.9.7 long message (lng) the received hdlc message length is determined to be greater than the maximum allowable message size per the maxsel bit field in section 6.6.8 . reason:  incorrect message transmission from distant end. effects:
basic operations 28500-DSH-002-C mindspeed technologies ? 140 mindspeed proprietary and confidential  when the message reaches the top of the internal fifo, the hdlc message up to the maximum legal length is copied to shared memory buffers and the buffer status descriptor is written (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ) with onr = host, error = lng.  eom interrupt with rxlng error status (if errien = 1 in section 6.6.4 and section 6.7.4 ).  the rslp scans for the opening flag of the next hdlc message.  rdma is not affected and continues shared memory buffer processing. channel level recovery actions:  none required. 8.2.9.8 short message (sht) the total received hdlc message size (between open/close flags) is determined to be less than the number of fcs bits specified for that channel plus one octet. for exam ple, a channel configured for 16-bit fcs must receive a minimum of three octets, one octet of payload and two octe ts of fcs, to avoid a short message error. in this example, receiving only two octets is considered a short message. reasons:  bit errors during transmission.  incorrect message transmission from distant end. effects:  rxsht interrupt (if idleien = 1 in section 6.6.2 ).  rslp resumes scanning for opening flag of the next hdlc message.  rdma is not affected and continues shared memory buffer processing. notice that a short message?s contents are not transferred to memory, therefore no message descriptor or data buffer is consumed by a short message. channel level recovery actions:  none required. 8.3 transparent mode cx28500 supports a completely transparent mode where no distinction is made between information and non- information bits in the channel bit stream. this mode is assigned on a per-channel and per-direction basis by the protocol bit field in section 6.6.2 and section 6.7.2 . note: any message that ends with an error (any error except for an overfl ow) and for which the entire message (regardless of its length) still resides in the internal slp buffer (meaning no data has yet been transferred to the internal channel fifo), cx28500 generates a sht interrupt and does not transfer an y of that message to a shared memory buffer. in this case, no other indication is given for the errore d message, thus saving pci bandwidth as well as shared memory buffer space. since the rxsht interrupt in this case is repor ted immediately, its interrupt descriptor can arrive in the shared memory interrupt queue before an earlier message that remains queued in the internal dma channel fifo. hence, interrupts from these two messages may appear out of sequence with respect to their actual order of arrival.
basic operations 28500-DSH-002-C mindspeed technologies ? 141 mindspeed proprietary and confidential 8.3.1 message configuratio n bits?transparent mode the transmit buffer descriptor contains a group of bits that specify the data to be transmitted after the end of a transparent mode message. the bits are specified as follows:  idle code specification, ic  inter-message pad fill count, padcnt  send an abort sequence, abort 8.3.1.1 idle code idle code (ic) bit field selects one of a set of idle pad fill octets to be sent after the current mess age is transmitted in the event the next message descriptor is unavailable (i.e ., host-owned) or inter-messa ge pad fill is requested via padcnt. the default idle code in transparent mode is all 1s, a silent signal. 8.3.1.2 inter-message pad fill pad count (padcnt) bit field specifies how many pad fill octets (selected by ic) are transmitted between messages. padcnt specifies the minimum number of pad fill octets plus one, as follows: 1. padcnt = 0: one ic 2. padcnt = 1: two ics 3. padcnt = 2: three ics 4. etc... 8.3.1.3 ending a message with an abort or sending an abort sequence when the abort field is non-zero in any cx28500-owned transmit buffer descriptor, cx28500 interprets this as a request to end an in-progress message with the abort sequence. abort sequence for transparent mode is defined to be a sequence of all 1s. the abort sequence is terminated only when a new cx28500-owned message descriptor with a non-zero blen becomes available. in this case, cx28500 resynchronizes the start of the next message transmission to the time slot marked as the first time slot on that channel. if abort 0, and the prior buffer descriptor on that channel contained eom = 1, (i.e., the previous buffer descriptor ended a message), the abort command is simply ignored and cx28500 moves onto the next message descriptor. the host can set eom = 1 in any transmit buffer descriptor to separate this transparent mode ?message? from the next message, according to the ic and padcnt bit fi elds. unlike hdlc mode, the number of pad fill octets transmitted equals padcnt plus one an d no flag characters are inserted. 8.3.2 transmit events transmit events are informational in nature and require no recovery actions. note: message configuration bits are also used in hdlc mode, but their meaning is slightly different. refer to section 8.2.5 .
basic operations 28500-DSH-002-C mindspeed technologies ? 142 mindspeed proprietary and confidential 8.3.2.1 end of buffer [eob] reason:  tdma reached the end of a buffer by servicing a number of octets equal to the blen bit field in the transmit buffer descriptor. note that eob and eom are not coincident and thus generate two separate events. effects:  txeob interrupt (if eobien = 1 in transmit buffer descriptor).  cx28500 continues with normal message processing . if the tdma does not get more data from shared memory before the internal channel fifo becomes empty and the tslp needs to output another data bit, tslp generates an underflow error. 8.3.2.2 end of message [eom] reason:  tslp has transmitted (actually, transferred to the tsiu) the last bit of a data buffer and the transmit buffer descriptor signified the end of a message with bit field eom = 1. note that eob and eom are not coincident and thus generate two separate events. effects:  txeom interrupt (if eomien = 1 in section 6.7.2 ).  tslp and tdma continue normal message processing. if the tdma does not get more data from shared memory before the internal channel fifo becomes empty and the tslp needs to output another data bit, tslp outputs pad fill octets un til more data is available. 8.3.3 receive events receive events are informational in nature and require no recovery actions. 8.3.3.1 end of buffer [eob] reason:  transparent mode receive channels have no concept of a ?message? boundary. hence, all received data is simply written to a shared memory da ta buffer until that buffer is filled according to the number of octets specified by the bit field blen in the receive buffer descriptor. effects:  eob interrupt (if eobien = 1 in receive buffer descriptor).  rdma and rslp continue normal processing. 8.3.3.2 end of message (eom) reason:  rslp must force an end of a message due to a receive error condition. error conditions include overflow, cofa, or oof. effects:  rdma sets bit field eom = 1 in re ceive buffer status descriptor (if inhrbsd = 0 in section 6.6.5 ).
basic operations 28500-DSH-002-C mindspeed technologies ? 143 mindspeed proprietary and confidential  rxeom interrupt (if errien = 1 in section 6.6.5 ) with the appropriate rxerr status.  rslp continues normal processing after the error condition has ended.  rdma is not affected and continues shared memory buffer processing. 8.3.3.3 frame recovery (frec) reason:  siu detects the serial interface has transitioned from an out-of-frame to an in-frame condition. if the roof pin is used as an out-of-frame indication, a frec interrupt is generated only after one full frame without any oof assertion is detected. if the roof pin is used as a general purpose interrupt input, a sport (serial port) interrupt is generated. effects:  frec/sport interrupt (if oofien = 1 in ta bl e 6 - 2 8 , rsiu port configuration register ).  rslp and rdma continue normal processing. 8.3.3.4 receive cofa recovery (rcrec) reason:  siu terminates the internal cofa condition due to a rsync/stb pulse followed by at least one frame for this port without another unexpected rsync/stb pulse. effects:  rcrec interrupt (if cofaien = 1 in ta bl e 6 - 2 8 , rsiu port configuration register ).  rslp and rdma continue normal processing. 8.3.4 transmit errors transmit errors are service-affecting and require a corrective action by the host to resume normal processing. 8.3.4.1 transmit underrun [buff] same as hdlc mode. reasons:  degradation of the host subsystem or application software.  buffer descriptor containing the continuation of a message is host-owned.  pci bus congestion. effects:  txbuff interrupt (if buffien = 1 in section 6.7.2 ).  transmit channel enters deactivate state, wher ein tslp sends a repetitive all 1s sequence.  tdma may read more buffers to refill the internal channel fifo (because this process is asynchronous to the tslp), but eventually the tdma stops servicing this channel because the tslp has stopped sending data. channel level recovery actions:  transmit channel complete reactivation is required.
basic operations 28500-DSH-002-C mindspeed technologies ? 144 mindspeed proprietary and confidential 8.3.4.2 transmit change of frame alignment (cofa) reason:  signal failure, glitch, or realignment caused by the ph ysical interface sourcing the tsync/stb input signal. effects:  causes serial interface to enter cofa condition until a tsync/stb pulse arrives and is followed by at least one frame for this port, without another unexpected tsync/stb pulse.  for every active channel on the respective port, tslp pl aces channels into the deactivate state, wherein tslp sends a repetitive all ones sequence.  transmit output is three-stated. channel level recovery actions:  transmit channel complete reactivation is required. 8.3.5 receive errors receive errors are service-affecting and may require a corrective action by the host to resume normal processing. 8.3.5.1 receive overflow [buff] same as hdlc mode. reasons:  degradation of host subsystem performance.  shortage of shared memory buffers. the receive bu ffer cx28500 needs to fill is presently host-owned.  pci bus congestion. effects:  rxbuff interrupt (if buffien = 1 in section 6.6.2 ).  data received during an overflow condition is discarded.  data in the internal fifo is copied to shared memory, the receive buffer status descriptor is written with onr = host, eom = 1, error = buff (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ).  if errien is set in section 6.6.4 and section 6.7.4 , an rxerr interrupt is generated, indicating an rxbuff overflow.  when the overflow condition ends (i.e., space becomes available in the channel fifo), rslp automatically restarts data processing. however, rslp ignores all time slots until reaching the time slot marked ?first.?  rdma is not affected and continues shared memory buffer processing. channel level recovery actions:  if possible, increase internal fifo size assigned to this channel. for this action, the channel must first be deactivated.  if necessary, alleviate pci bus congestion.  notice that channel reactivation is not required.
basic operations 28500-DSH-002-C mindspeed technologies ? 145 mindspeed proprietary and confidential 8.3.5.2 receive change of frame alignment (cofa) same as hdlc mode. reason:  signal failure, glitch, or realignment caused by the physical interface sourcing the rsync or tstb input signal. effects:  causes serial interface to enter cofa condition until the rsync/tstb pulse is followed by at least one frame for this port, without another unexpected rsync/tstb pulse.  current message processing is ended for every active channel on this port. all data received prior to the cofa condition is copied to shared memory buffers, and the receive buffer status descriptor is written with onr = host and error = cofa (if inhrbsd = 0 in section 6.6.4 and section 6.7.4 ). the only exception to this description happens when the cofa condition is detected within the first few bytes after channel activation or after the channel suffered an overflow or another cofa, as described in section 8.3.5.4 .  receive cofa interrupt (if cofaien = 1 in table 6-28, rsiu port configuration register ). when the cofa condition ends, rslp restarts data processing automatically; however, all time slots are ignored until reaching the time slot marked ?first.?  rdma is not affected and continues shared memory buffer processing. channel level recovery actions:  none required. 8.3.5.3 out of frame (oof) same as hdlc mode. reason:  roof input pin is asserted (high) because the attached physical layer device is unable to recover a valid, framed signal. only time slots marked with an oof assertion are affected, and not the whole port. effects:  oof interrupt (if oofien = 1 and oofabt = 1 in ta bl e 6 - 2 8 , rsiu port configuration register ).  if bit field oofabt = 0, rslp and rdma continue as if there are no errors and transfer received data into shared memory buffers normally.  if bit field oofabt = 1, all incoming data is replaced by all ones (0xff) data sequence. normal data processing resumes when the roof input pin is deasserted (low), indicating the oof condition has ended.  rdma is not affected and continues shared memory buffer processing. channel level recovery actions:  none required.
basic operations 28500-DSH-002-C mindspeed technologies ? 146 mindspeed proprietary and confidential 8.3.5.4 short cofa (sht cofa) a short cofa interrupt is generated for any transparent mode message whose reception is ended due to a cofa error and for which no data was transferred from rslp to rdma or to shared memory. in this case, no other indication is provided for this errored message , thus saving pci bandwidth and host buffers. reason:  signal failure, glitch or realignment caused by the physical interface sourcing the rsync or stb input signal. effects:  rxsht interrupt (if idleien = 1 in section 6.6.2 ).  rslp restarts channel operation as soon as the cofa condition is recovered and the channel reaches its first assigned time slot.  rdma is not affected and continues shared memory buffer processing. notice that no shared memory buffer descriptors are consumed. channel level recovery actions:  none required. note: only transparent mode cofa creates such a scenario. the exact scenario is as follows: a cofa condition happens within the next few bytes after an abnormal message termination (i.e., a prior cofa or overflow error) or after a channel activation.
28500-DSH-002-C mindspeed technologies ? 147 mindspeed proprietary and confidential 9.0 self-servicing buffers the transmit and receive buffer descri ptors and buffer status descriptors are designed to fac ilitate a mechanism known as self-servicing buffers. this mechanism allows th e host to configure cx28500 to fill a table of data buffers as it receives a complete message through a receive channel, then empty the same list of data buffers through a transmit channel without any further host intervention. the self-servicing buffer mechanism works as follows: 1. host initializes message descriptor table in shared memory. 2. host configures receive channel head pointer to point to first message descriptor. 3. host configures transmit channel head pointer to point to the same message descriptor. 4. the owner bit field in the buffer descriptor is set to 0. for the transmitter, this means the buffer is owned by the host. for the receiver, this means the buffer is owned by cx28500. 5. the np bit field in the transmit buffer descriptor is set to 0. this allows the cx28500 to poll the owner bit field of the buffer descriptors. 6. both receive and transmit channels are activated. 7. as the receiver detects an incoming message and begins filling the first dat a buffer, the transmitter remains idle and polls the owner bit in the buffer descriptor. 8. when the receiver fills the first buffer , it writes the buffer status descript or (setting the owner bit field to 1) and then moves on to the next message descriptor. although the data buffer is not going to be returned to the host, the inhibit receive buffer status descriptor option should not be enabled (inhrbsd = 0 in rdma channel configuration register). in other words, the cx28500 must be allowed to overwrite the buffer descriptor with the buffer status descriptor. 9. during the next poll transaction, the transmit channel detects if the owner bit field is set to 1 in the first buffer descriptor and assumes ownership. the transmitter then begins emptying the first data buffer and moving data to the serial port. the inhibit transmit buffer status descriptor option must be disabled for cx28500 to return ownership to the host (i.e., inhtbsd = 0 in tdma channel configuration register). in other words, the cx28500 must be allowed to overwrite the buffer descriptor with the buffer status descriptor. 10. upon detecting an end of message, the receiver writes the buffer status descriptor, marking the buffer as an end of message and setting the buffer length (blen) to indicate the amount of data contained in this buffer. 11. when the transmitter reads an end of message buffer, it sends the blen amount of data out the serial port and writes the buffer status descriptor (setting the owner bit field to 0), then moves onto the next buffer or enters the idle state (if the next bu ffer is still owned by the receiver). 12. steps 6-10 are repeated continuously, until the host deactivates either the receive or transmit channel. it is important to note that for self-servicing buffers, the host does not need to write to any descriptors for receive or transmit operations. cx28500 writes the receive buffer st atus descriptor, which is subsequently used as the transmit buffer descriptor.
self-servicing buffers 28500-DSH-002-C mindspeed technologies ? 148 mindspeed proprietary and confidential to provide a mechanism for the self-served transmitter to recover from a receiver error, rdma automatically sets abort 0 in the buffer descriptor upon detection of any receive error (eom is also set to one). in hdlc mode, abort 0 in the buffer descriptor causes the transmitter to send an abort sequence. in transparent mode, abort 0 in the buffer descriptor causes pad fill transmission until the next message is av ailable. in either case, subsequent message transm ission remains unaffected. two things are important to notice: 1. if the transmitter is slower than the receiver (even by a tiny fraction), it will not empty the buffers fast enough and the receiver will eventually overflow the internal buffers. 2. if the receiver marks end of message (eom) in a buffer status descriptor, it also changes the blen field to a value that is necessarily lower than the original value. the transmitter sends the correct number of bytes and relinquishes ownership, but it does not return the blen to the original value. the receiver, upon wrapping around and reaching this buffer will see the new (lower) value of blen instead of the older (higher) value. over a long period of time, this can cause problems as buffer s become shorter and shorter. the solution is to use buffers that are all the same length, and periodically test the buffer descriptor table to return the blen fields to the original value (be careful, though, not to overwrite the blen field of a buffer that the transmitter has not yet begun sending).
28500-DSH-002-C mindspeed technologies ? 149 mindspeed proprietary and confidential 10.0 electrical and mechanical specification 10.1 electrical and environmental specifications 10.1.1 absolute maximum ratings stressing the device parameters beyond absolute maxi mum ratings may cause permanent damage to the device. this is a stress rating only. functional operation of the device at these or any other conditions beyond those listed in the operational sections of this spec ification is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. table 10-1. absolute maximum ratings parameter symbol value unit minimum maximum core power supply vdd_c ?0.5 3.3 v i/o power supply vdd_io ?0.5 4.6 v 5 v tolerant power supply vgg vdd_io?0.5 6.0 v constant voltage on any signal pin v i ?1.0 vgg + 0.3 (not exceeding 6v) v constant current on any signal pin i i ?10 10 ma transient current on any signal pin at 25 c latchup ? 300 ma transient current on any signal pin at 125 c latchup ? 150 ma operating junction temperature t j ?40 125 c storage temperature t s ?55 125 c vapor phase soldering temperature (1 min.) t vsol ? 220 c
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 150 mindspeed proprietary and confidential 10.1.2 recommended operating conditions 10.1.3 electrical characteristics table 10-2. recommended 3.3 v operating conditions parameter symbol value unit minimum maximum power supply vdd_c 2.375 2.625 v i/o power supply vdd_io 3.135 3.465 v 5 v tolerant power supply vgg vdd_io 5.25 v industrial temperature range t ac (3) ?40 +85 c high-level input voltage v ih (1) 2.0 vgg + 0.3 v low-level input voltage v il (1) 00.8v high-level output current source i oh ? 400 a low level output current sink i ol ?4ma output capacitive loading c ld ?85pf core supply current idd_c ? 1 a i/o supply current idd_io ? 0.3 a continuous power dissipation p d ?3.7 (2) w footnote: (1) apply to all pins, except the pci interface, which is defined in table 10-4 . (2) the 3.7 w maximum continuous power dissipation is observed for an application utilizing the comple te potential of the device, w ith voltages that deviate 5% higher than nomin al, and with 60 pf capacitance load on the i/os. any real-world application will see much lower figures. (3) applies to all device func tions, except the jtag interface, for which room temperature is recommended. (4) please refer to minds peed smt lead-free packages applic ation note (2xxxx-app-001-a) for the pb-free (rohs) devices and for the detail explination of how jedec determines the re flow temperatures based on package thickness. table 10-3. dc characteristics for 3.3 v operation parameter symbol value units high-level output voltage v oh 2.4 v low-level output voltage v ol 0.4 v input leakage current i l ?10 to 10 a three-state leakage current i oz ?10 to 10 a resistive pullup current i pr 20 to 250 a
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 151 mindspeed proprietary and confidential 10.1.4 power-up sequencing power up sequencing involves the order of powering up the i/o and core supplies and the period of time between powering up these supplies. when the i/o supply (vdd_io) is powered up first, the output drivers can be in an indeterminate state until the core supply (vdd_c) is powered up. if the delay in the power sequence is too long (several ms or more), the unknown state of the output drivers can cause system problems. the recommended power up sequence is first 5 v (vgg), then 3.3 v (vdd_io), and then 2.5 v (vdd_c). the i/o supply must be powe red up before the core supp ly. otherwise, a high curr ent will be drawn until the i/o supply is powered up. the time from the detection of i/o power to the disabling of output drivers and the time from the detection of core power to the ena bling of output drivers will not exceed 100 ns. therefore, it is recommended that the core is powered up more than 100 ns after i/o. if core is powered up during the first 100 ns after i/o power- up, the device may draw more current until the first 100 ns are elapsed. 10.2 timing and switching specifications 10.2.1 overview this section defines the timing and switching characteri stics of cx28500. the major subsystems include the host interface, the expansion bus interface, and the serial interface. the host interface is peripheral component interface (pci) compliant. for other references to pci, see the pci local bus specification , revision 2.1, june 1, 1995. the expansion bus and serial bus interfaces are sim ilar to the host interface timing characteristics; the differences and specific characteristics common to either interface are further defined. 10.2.2 host interface (pci) timi ng and switching characteristic reference the pci local bus specification, revision 2.1 , june 1, 1995 for information the following:  indeterminate inputs and metastability  power requirements, sequencing, decoupling  pci dc specifications  pci ac specifications  pci v/i curves  maximum ac ratings and device protection table 10-4. pci interface dc specifications (1 of 2) symbol parameter condition min max units vdd_io supply voltage ? 3 3.6 v v ih input high voltage ? 0.5 vdd_io vgg + 0.3 v v il input low voltage ? ?0.5 0.3 vdd_io v i il input leakage current (1) 0 < v in < vdd_io ? +/-10 a v oh output high voltage i out = ?500 a0.9 vdd_io ? v v ol output low voltage (2) i out = 1500 a ? 0.1 vdd_io v c out /c in /c io output, input, and i/o pin capacitance ? ? 10 pf c clk pclk pin capacitance ? 5 12 pf
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 152 mindspeed proprietary and confidential c idsel idsel pin capacitance (3) ??8pf l pin pin inductance ? ? 20 nh footnote: (1) input leakage currents include hi-z output leakage for all bi directional buffers with three-state outputs. (2) signals without pullup resistors mu st have 3 ma low output current . signals requiring pullup must have 6 ma; the latter include frame*, trdy*, irdy*, devsel*, stop*, serr*, and perr*. (3) lower capacitance on this input-only pin a llows for non-resistive coupling to ad[xx]. table 10-5. pci clock (pclk) waveform parameters, 3.3 v clock symbol parameter min 33 mhz max 33 mhz min 66 mhz max 66 mhz units t cyc clock cycle time (1) 30 infinite 15 30 ns t high clock high time 11 ? 6 ? ns t low clock low time 11 ? 6 ? ns ? clock slew rate (2) 1 4 1.5 4 v/ns v ptp peak-to-peak voltage 0.4 vdd_io ? 0.4 vdd_io ? v footnote: (1) cx28500 works with any clock frequency betwee n dc and 66 mhz, nominally. the clock freq uency may be changed at any time during operation of the system as long as clock edges remain monotonic, and minimum cycle and high and low times are not violated. the clock may only be stopped in a low state. (2) rise and fall times are specified in terms of the edge rate meas ured in v/ns. this slew rate must be met across the minimum pea k-to- peak portion of the clock waveform. figure 10-1. pci clock (pcl k) waveform, 3.3 v clock table 10-4. pci interface dc specifications (2 of 2) symbol parameter condition min max units 0.5 0.4 0.3 0.6 0.2 vdd_io t high t cyc t low v ptp (min) 500052_059 vdd_io v cc v cc v cc
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 153 mindspeed proprietary and confidential table 10-6. pci reset parameters symbol parameter min max units t rst reset active time after power stable 1 ? ms t rst_clk reset active time after clock stable 100 ? s t rst-off reset active to float delay ? 40 ns t rrsu req64 to rst setup time 10 t cyc ?ns t rrh rst to req64 hold time 0 50 ns table 10-7. pci input/output timing parameters symbol parameter min 33 mhz max 33 mhz min 66 mhz max 66 mhz units t val pclk to signal valid delay?bused signal ( 1, 2) 211210ns t val (ptp) pclk to signal valid delay?point to point ( 1, 2) 212210ns t val (o.d.) pclk to signal valid delay?open drain ( 5) 211210ns t on float to active delay (3) 2?2?ns t off active to float delay (3) ?28?14ns t ds input setup time to clock?bused signal (2) 7?4?ns t su (ptp) input setup time to clock?point to point (2) 10, 12 ? 5 ? ns t dh input hold time from clock 0 (4) ?0 (4) ?ns footnote: (1) minimum and maximum times are eval uated at 80 pf equivale nt load. actual test capacitance may vary, and results should be corre lated to these specifications. (2) req* and gnt* are the only point-to-point si gnals, and have differ ent output valid delay and input setup times than do bused si gnals. gnt* has a setup of 10 ns; req* has a setup of 12 ns for 33 mhz. (3) for purposes of active/float timing measuremen ts, the hi-z or off state is defined to be when the total current delivered throu gh the component pin is less than or e qual to the leakage current specific ation at 80 pf equivalent load. (4) actual measurements were done with 0.5 ns for test equipment guardband. (5) the only open-drain outputs in the pci interfac e are the inta# signal and the serr# signal. table 10-8. pci i/o measure conditions symbol parameter value unit v th voltage threshold high (1) 0.6 vdd_c v v tl voltage threshold low (1) 0.2 vdd_c v v test voltage test point 0.4 vdd_c v v max maximum peak-to-peak ( 2) 0.4 vdd_c v ? input signal edge rate 1 v/ns footnote: (1) the input test is done with 0.1 vdd_c of overdrive (over v ih and v il ). timing parameters must be met with no more overdrive than this. production testing can use different vo ltage values, but must correlate re sults back to th ese parameters. (2) v max specifies the maximum peak-to-peak volt age waveform allowed for measuring input timing. production testi ng can use different voltage values, but must correlate results back to these parameters.
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 154 mindspeed proprietary and confidential figure 10-2. pci output timing waveform figure 10-3. pci input timing waveform v th v tl v test v test (3.3 v signaling) t val t on t off pclk output delay three-state output output current leakage current 500052_060 clk input v th v tl v test t ds t dh v max v test v th v tl inputs valid 500052_061
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 155 mindspeed proprietary and confidential 10.2.3 expansion bus (ebus) timi ng and switching characteristics the ebus timing is derived directly from the pci clock (pclk) input into cx28500. the ebus clock can have the same frequency as the pci cl ock, or it can have half the frequency of the pci clock. this option is configured in the ebus configuration register. please see ta b l e 6 - 1 2 for more detail. table 10-9. ebus reset parameters symbol parameter min max units t rst_off active to inactive delay (1) ?28 ns footnote: (1) for purposes of active/float timing measuremen ts, the hi-z or off state is defined to be when the total current delivered throu gh the component pin is less than or equal to the leakage current specification. figure 10-4. ebus reset timing table 10-10. ebus input/output timing parameters symbol parameter min max units t val eclk to signal valid delay?bused signal ( 1) ?4 6 ns t val (ptp) eclk to signal valid delay?point to point (1) 212ns t on float to active delay (2) ?5 ? ns t off active to float delay (2) ?20 ns t ds input setup time to clock ? bused signal 18 ? ns t dh input hold time from clock 0 ? ns footnote: (1) minimum and maximum times are eval uated at 80 pf equivale nt load. actual test capacitance may vary, and results should be corre lated to these specifications. (2) for purposes of active/float timing measuremen ts, the hi-z or off state is defined to be when the total current delivered throu gh the component pin is less than or e qual to the leakage current specific ation at 80 pf equivalent load. general note: the ebus reset is dependent on the prst* (pci reset) signal being asserted low. pci reset ebus three-state output ebus input t rst_off reset period three-state input ignored 500052_062
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 156 mindspeed proprietary and confidential table 10-11. ebus input/output measure conditions symbol parameter value units v th voltage threshold high (1) 0.6 vdd_io v v tl voltage threshold low (1) 0.2 vdd_io v v test voltage test point 0.4 vdd_io v v max maximum peak-to-peak ( 2) 0.4 vdd_io v ? input signal slew rate 1.5 v/ns footnote: (1) the input test for the 3.3 v envi ronment is done with 0.1*vdd_io of overdrive. timing parameters must be met with no more overdrive than this. production testing may us e different voltage values, but must corre late results back to these parameters. (2) v max specifies the maximum peak-to-peak vo ltage waveform allowed for measuring input timing. producti on testing may use different voltage values, but must correlate results back to these parameters. figure 10-5. ebus output timing waveform figure 10-6. ebus input timing waveform 500052_080 eclk output delay v th v tl v test v test t val 500052_081 eclk input v th v tl v test v test v test v max v th v tl t ds t dh
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 157 mindspeed proprietary and confidential 10.2.4 ebus arbitratio n timing specification figure 10-7. ebus write/read cycle, intel-style general note: 1. hlda assertion depends on the external bus arbiter. while hold and hlda are both deasserted, musycc places shared ebus signals in high impedance (three-state, shown as dashed lines). 2. one eclk cycle after hlda assertion, musycc outputs valid command bus signals: ebe, ale, rd*, and wr*. 3. two eclk cycles after hlda assertion, musycc outputs valid ead address signals. 4. ale assertion occurs 3 eclk cycles after hold and hlda are both asserted. alapse inserts a variable number of eclk cycles to extend ale high pulse width and ead address interval. 5. ead address remains valid for one eclk cycle after ale falling edge. during a write transaction, musycc outputs valid ead write data one eclk prior to wr* assertion. during a read transaction, ead data lines are inputs. 6. elapse inserts a variable number of eclk cycles to extend rd*/wr* low pulse width and ead data intervals. read data inputs are sampled on eclk rising edge coincident with rd* deassertion. 7. ead write data and ebe byte enables remain valid for one eclk cycle after rd*/wr* deassertion. 8. one eclk after rd* or wr* deassertion, hold is deasserted and the bus is parked (command bus deasserted, ead three-state). the bus parked state ends when hlda is deasserted. 9. command bus is unparked (three-stated) one eclk after hlda deassertion; two different unpark phases are shown, indicating the dependence on hlda deassertion. if hlda remained asserted until the next bus request, then command bus remains parked until one eclk cycle following the next hold assertion. caution: whenever hlda is deasserted, all shared ebus signals are forced to three-state after one eclk cycle, regardless of whether the ebus transaction was completed. musycc does not reissue or repeat such an aborted transaction. 10. blapse inserts a variable number of eclk cycles to extend hold deassertion interval until the next bus request. 11. the address line a31 must be asserted in all transactions. ecl k hold hlda ead[31:0] ebe[3:0]* ale rd* (write) wr* (write) rd* (read) see notes elapse = 0 1 alapse = 0 blapse = 0 2345678910 wr* (read) data address (11) byte enables from ebus configuration descriptor 500052_067
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 158 mindspeed proprietary and confidential figure 10-8. ebus write/read cycle, motorola-style eclk br* bg* bgack* ead[31:0] ebe[3:0]* as* r/wr* (read) r/wr* (write) ds* see notes elapse = 0 1 data alapse = 0 blapse = 0 address (11) 2 34 5 678910 general note: 1. bg* assertion depends on the external bus arbiter. while bg* and br* are both deasserted, musycc places shared ebus signals in high impedance (three-state, shown as dashed lines). 2. one eclk cycle after bg* assertion, musycc outputs valid command bus signals: ebe, as*, r/wr*, and ds*. 3. two eclk cycles after bg* assertion, musycc outputs valid ead address signals. bgack* assertion occurs three eclk cycles after bg* and br* are both asserted. 4. alapse inserts a variable number of eclk cycles to extend as* high pulse width and ead address interval. 5. ead address remains valid for one eclk cycle after as* falling edge. during a write transaction, musycc asserts r/wr* and outputs valid ead write data one eclk prior to ds* assertion. during a read transaction, ead data lines are inputs. 6. elapse inserts a variable number of eclk cycles to extend ds* low pulse width and ead data interval. read data inputs are sampled on eclk rising edge coincident with ds* deassertion. 7. ead write data, ebe, r/wr*, and as* signals remain valid for one eclk cycle after bgack* and ds* are deasserted. 8. one eclk after bgack* deassertion, the br* output is deasserted and the bus is parked (command bus deasserted, ead three-state). the bus parked state ends when the external bus arbiter deasserts bg*. 9. command bus is unparked (three-stated) one eclk after bg* deassertion; two different unpark phases are shown, indicating the dependence on bg* deassertion. if bg* remained asserted until the next bus request, then command bus remains parked until one eclk cycle following the next br* assertion. caution: whenever bg* is deasserted, all shared ebus signals are forced to three-state after one eclk cycle, regardless of whether the ebus transaction was completed. musycc does not reissue or repeat such an aborted transaction. 10. blapse inserts a variable number of eclk cycles to extend br* deassertion interval until the next bus request. 11. the address line a31 must be asserted in all transactions. 500052_068 byte enables from ebus configuration descriptor
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 159 mindspeed proprietary and confidential 10.2.5 serial interface timing and switching characteristics table 10-12. serial interface clock (rclk, tclk) parameters symbol parameter min max units f c clock frequency dc 52 mhz t r clock rise time for non-hssi ports (6?31) ? 20 ns clock rise time for hssi ports (0?5) ? 3 ns t f clock fall time for non-hssi ports (6?31) ? 20 ns clock fall time for hssi ports (0?5) ? 3 ns ? clock duty cycle 40 60 % figure 10-9. serial interface clock (rclk,tclk) waveform table 10-13. serial interface input/output timing parameters symbol parameter min max units t val (2) clock to signal valid delay for non-hssi ports (6?31) 2 20 ns clock to signal valid delay for hssi ports (0?5) 2 8 ns t ds (3) data setup time for non-hssi ports (6?31) 8 ? ns data setup time for hssi ports (0?5) 3 ? ns t dh (3) data hold time for non-hssi ports (6?31) 8 ? ns data hold time for hssi ports (0?5) 4 ? ns notes: 1. parameters were characte rized with c load = 70 pf 2. output delay 3. input signals 1/f c t r t f rclk, tclk 500052_069
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 160 mindspeed proprietary and confidential table 10-14. serial interface input/output measure conditions symbol parameter value units v th voltage threshold high (1) 0.6 vdd_io v v tl voltage threshold low (1) 0.2 vdd_io v v test voltage test point 0.4 vdd_io v v max maximum peak-to-peak ( 2) 0.4 vdd_io v ? input signal slew rate 1.5 v/ns c ld maximum load capacitance?output and i/0 70 pf footnote: (1) the input test for the 3.3 v environment is done with 0.1*v dd_io of overdrive. timi ng parameters must be met with no more overd rive than this. production testing may use diff erent voltage values, but must correlate results back to these parameters. (2) v max specifies the maximum peak-to-peak volt age waveform allowed for measuring input timing. production testi ng may use different voltage values, but must correlate results back to these parameters. figure 10-10. serial interface data input waveform v th v tl v test v max t ds t dh v test v test v th v tl v max v test t ds t dh v test v test v th v tl rcl k rd at (rising) rd at (falling) 500052_0 7
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 161 mindspeed proprietary and confidential figure 10-11. serial interface data delay output waveform v th v tl v test v max v test v test v th v tl v test tclk tdat (rising) tdat (falling) t val v max v test v test v th v tl t val 500052_071
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 162 mindspeed proprietary and confidential figure 10-12. transmit and receive t1 mode f-bit 0 1 3 2457 6 7 6 0 rclk rsync-rise(a) rdat a-rise(a) f-bit 0 1 2 4 3560 7 7 6 rsync-rise(b) rdat -fall(b) f-bit 0 1 3 2457 6 7 6 0 rsync-fall(c) rdata-r ise(c) f-bit 0 1 2 4 3560 7 7 6 rsync-fall(d) rdat -fall(d) f-bit 012 4 35 60 7 7 6 tclk tsync-rise(a) tdat-r ise(a) f-bit 0 1 3 2457 6 7 6 0 tsync-rise(b) tdata -fall(b) f-bit 012 4 35 60 7 7 6 tsync-fall(c) td at-r ise(c) f-bit 0 1 3 2457 6 7 6 0 tsync-fall(d) tdata -fall (d) 500052_072 general note: 1. t1 mode employs 24 time slots (0?23) with 8 bits per time slot (0?7) and 1 frame-bit every 193 clock periods. one frame of 193 bits occurs every 125 s (1.544 mhz). 2. rsync and tsync must be asserted for a minimum of 1 clk period. 3. cx28500 can be configured to sample rsync, tsync, rdat, and tdat on either a rising or falling clock edge independently of any other signal sampling configuration. 4. relationships between the various configurations of active edges for the synchronization signal and the data signal are shown using a common clock signal for receive and transmit operations. note the relationship between the frame bit (within rdat, tdat) and the frame synchronization signal (e.g., rsync, tsync). 5. all received signals (e.g., rsync, rdat, tsync) are ?sampled? in on the specified clock edge (e.g., rclk, tclk). all transmit data signals (tdat) are latched on the specified clock edge. 6. in configuration (a), synchronization and data signals are sampled/latched on a rising clock edge. 7. in configuration (b), synchronization signal is sampled on a rising clock edge and the data signal is sampled/latched on a falling clock edge. 8. in configuration (c), synchronization signal is sampled on a falling clock edge and the data signal is sampled/latched on a rising clock edge. 9. in configuration (d), synchronization and data signals are sampled/latched on a falling clock edge.
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 163 mindspeed proprietary and confidential figure 10-13. transmit and receive channelized non t1 (i.e., n x 64) mode 012 4 3568 7 m-1 m-2 9 rclk rsync-rise(a) rdat a-rise(a) 0123 5 4679 8 m-1 m-2 rsync-rise(b) rdat -fall(b) 012 4 3568 7 m-1 m-2 9 rsync-fall(c) rdat a-rise(c) 01 2 3 5 4679 8 m-1 m-2 rsync-fall( d) rdat -fall(d) 0123 5 4679 8 m-1 m-2 tclk tsync-rise(a) tdat-r ise(a) 012 4 3568 7 m-1 m-2 9 tsync-rise(b) tdata -fal l(b) 0123 5 4679 8 m-1 m-2 tsync-fall(c) tdat- rise(c) 012 4 3568 7 m-1 m-2 9 tsync-fall(d) tdata -fall(d) 500052_073 general note : 1. e1 mode employs 32 time slots (0?31) with 8 bits per time slot (0?7) and 256 bits per frame and one frame every 125 s (2.048 mhz). 2. 2xe1 mode employs 64 time slots (0?63) with 8 bits per time slot (0?7) and 512 bits per frame and one frame every 125 s (4.096 mhz). 3. 4xe1 mode employs 128 time slots (0?127) with 8 bits per time slot (0?7) and 1024 bits per frame and one frame every 125 s (8.192 mhz). 4. rsync and tsync must be asserted for a minimum of 1 clk period. 5. cx28500 can be configured to sample rsync, tsync, rdat, and tdat on either a rising or falling clock edge independently of any other signal sampling configuration. 6. relationships between the various configurations of active edges for the synchronization signal and the data signal are shown using a common clock signal for receive and transmit operations. note the relationship between the frame bit (within rdat, tdat) and the frame synchronization signal (e.g. rsync, tsync). 7. all received signals (e.g., rsync, rdat, tsync) are sampled in on the specified clock edge (e.g. rclk, tclk). all transmit data signals (tdat) are latched on the specified clock edge. 8. in configuration (a), synchronization and data signals are sampled/latched on a rising clock edge. 9. in configuration (b), synchronization signal is sampled on a rising clock edge and the data signal is sampled/latched on a falling clock edge. 10. in configuration (c), synchronization signal is sampled on a falling clock edge and the data signal is sampled/latched on a rising clock edge. 11. in configuration (d), synchronization and data signals are sampled/latched on a falling clock edge. legend: m = nx8 bits, where m = number of time slots.
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 164 mindspeed proprietary and confidential 10.2.6 test and diagnostic interface timing table 10-15. test and diagnostic interface timing requirements symbol parameter minimum maximum units 1 tck pulse-width high 80 ? ns 2 tck pulse-width low 80 ? ns 3 tms, tdi setup prior to tck rising edge (1) 15 ? ns 4 tms, tdi hold after tck high (1) 20 ? ns footnote: (1) also applies to functional inputs for sample/preload and ex test instructions. table 10-16. test and diagnostic interface switching characteristics symbol parameter minimum maximum units 5 tdo hold after tck falling edge 0 ? ns 6 tdo delay after tck low ? 50 ns 7 tdo enable (low z) after tck falling edge 2 15 ns 8 tdo disable (high z) after tck low ? 25 ns general note: also applies to functional ou tputs for the extest instruction. figure 10-14. jtag interface timing 1 2 34 5 6 7 8 tdo tck tdi tms 500052_074
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 165 mindspeed proprietary and confidential 10.3 package thermal specification table 10-17. cx28500 package thermal resistance characteristics package mounting conditions airflow- lfm (1) (lms (2) ) thermal resistance (junction to ambient) = **c/w max. power (3) tac = 85 c tac = 70 c 580-pin tbga board-mounted 0 10 4 w 5.5 w 200 (1.02) 8.7 4.5 w 6.3 w 500 (2.54) 7.5 5.3 w 7.3 w general note: 1. lfm-linear feet per minute. 2. lms-linear meters per second. 3. junction to case temperature ( c): tjc =tac + ( ja x pd). tjc = ja x pd (measured) + tac (measured) where tjc = junction temperature (see table 10-1 ) ja = thermal resistance tac = ambient case temperature (see table 10-2 ) pd = power dissipation = vdd_c x idd (see table 10-1 )
electrical and mechanical specification 28500-DSH-002-C mindspeed technologies ? 166 mindspeed proprietary and confidential 10.4 mechanical specification figure 10-15. 580-pin bga package diagram 500052_046 a 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 b c d e f g h j k l m n p r t u v w y aa ab ac ad ae af ag ah aj ak al am an ap 10 11 4 6 5 corner detail b detail a e1 d1 bottom view side view top view detail b detail a e d e e g g b ca1 a ? b ? ? c ? c ccc c aaa ? a ? 0.10 00.30 c a 45? 0.35 mm chamfer (4 places) s s b s 00.10 c s p a a1 d d1 e e1 b c m n aaa ccc e g p 1.25 0.40 34.80 34.80 0.50 0.85 0.35 0.15 1.40 0.50 35.00 35.00 0.63 0.90 34 580 1.55 0.60 35.20 35.20 0.75 0.95 0.15 0.25 33.00 (bsc.) 33.00 (bsc.) 1.00 typ. dimensional references ref. min. nom. max.
28500-DSH-002-C mindspeed technologies ? 167 mindspeed proprietary and confidential appendix a: cx28500 pci bus latency and utilization analysis a.1 objective to check whether cx28500 internal fifos can withstand the time delays to their being serviced that are caused by a combination of pci latency and other channels requesting service without experiencing an underflow or overflow. further to analyze pci bus utilization. a.2 definitions a transmitter underflow (txbuff) is defined as the cond ition that exists when an output fifo for a specific channel is emptied before transmission of a complete hdlc frame. a receiver overflow (rxbuff) is caused when cx28500 d oes not service a channel in time, which in turn is caused by either excessive pci bus latency or other chan nel demands on the pci. an overflow is defined as the condition that exists when the input fifo for a specific channel is completely full and that channel receives more input data. maxdata is the maximum number of data cycles that ca n be transferred across the pci bus during one pci transaction. numch is the number of channels configured. a pci data transaction is defined as a pci transaction that involves a read or write burst of message data to or from the host memory. this does not include a read or write burst of a buffer descriptor (bd) nor of status bits. f pci is the pci clock rate in hz. f ch is the internal channel bit rate in bits per second. th is value takes into account the overhead caused by hdlc framing and of storing the status in the slp (serial line processor) fifo. the threshold of a receive channel rslp fifo (thr rx ) is the amount of data in bits that, when the amount of data in the fifo crosses this level, causes the channel to request service from the dma (direct memory access) controller. the threshold of a transmit channel tslp fifo (thr tx ) is the amount of data in bits that, when the amount of data in the fifo crosses this level, causes the channel to request service from the dma. the bufflen (bufflen) of a channel is the internal fifo length allocated to that channel for use between the slp and the dma.
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 168 mindspeed proprietary and confidential a.3 assumptions/modes of operation  each servicing of a channel is initiated by its channel number reaching the front of the service queue and is terminated after precisely one pci transaction regardless of whether that transaction moves data or buffer descriptor overhead. if a channel requires further servicing, the dma controller automatically replaces its request at the back of the service queue.  the dma aging-period is not relevant to pci latency when considering the worst case scenario.  an internal, fairly weighted, round-robin scheme is used to decide whether the next pci transaction is receive- based or transmit-based.  regardless of whether the pci bus works in 32-bit or 64-bit mode, maxdata has a maximum value of 32 dwords (to limit the time of any one data transaction).  the pci clock frequency is either 33 or 66 mhz.  the host causes no bottleneck in the operation of cx28500 and host access latency (trdy delay) is considered to be zero. hence, this model also assumes that no pci read transaction is ever retried due to target unavailability and the pci bridge fifo is la rge enough to accept continuous cx28500 transactions without becoming full.  an unchannelized port is considered for the purpose of calculations to be one channel. for the case of a tsbus interface, each virtual serial port (vsp) is considered to be one channel.  each packet is contained in one buffer in the host memory. if this is not the case, extra overhead per packet is associated with buffer descriptor management.  interrupt service is not taken into consideration since using status for every bd is more demanding on the pci. a.4 pci transaction timing each pci transaction is accompanied by an associated overhead. the two types of pci transaction and their associated overheads are outlined below. a.4.1 read a read transaction of x dwords of data including a host access latency of r cycles takes (3 + x + r) cycles for a 32- bit mode pci or (3 + [(x/2)] + r) cycles for a 64-bit mode pci. these include an address cycle and two bus turnaround cycles. a.4.2 write a write transaction of x dwords of data, including a host access latency of w cycles, ta kes (2 + x + w) cycles for a 32 bit mode pci or (2 + [(x/2)] + w) cycles for a 64 -bit mode pci. these include one address cycle and one bus turnaround cycle. note: with usage of the fast back-to-back feature of the pci, the number of turn around cycles can be reduced. however in the following cal culations the worst case has been considered so the maximum number of cycles has been used. note: with usage of the fast back-to-back feature of the pci, the number of turn around cycles can be reduced. however in the following cal culations the worst case has been considered so the maximum number of cycles has been used.
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 169 mindspeed proprietary and confidential a.5 receive messages when dealing with received messages, the full set of pci transactions processed by the dma controller, per channel, is as follows:  read bd: cx28500 performs a burst read of 2 dwords from host memory. this transaction takes (3 + 2 + r) cycles during 32-bit mode, or (3 + 1 + r) cycles during 64-bit mode.  data transfer: frame information is written to host memory until either the end of the memory buffer, the end of the message, or the pci bus is lost. in the general case, this transaction takes (2 + x + w) cycles for 32-bit mode or (2 + [(x/2)] + w) cycles for 64-bit mode. where x is the number of dwords transferred. the longest possible value of this interval is the remaining length of the pci latency timer or maxdata cycles. hence, the transaction may take (2 + maxdata + w).  write buffer status: this transaction takes (2 + 1 + w) cycles regardless of the 32- or 64-bit pci mode, if the eccmode bit of the global configuration register is clear (i.e., 0). when eccmode is set to 1, this transaction takes (2 + 2 + w) cycles in 32-bit pci mode, and (2 + 1 + w) cycles in 64-bit pci mode. this chapter was written with the former in mind (i.e., this transaction is always calculated as (2 + 1 + w) cycles, as this is the prevalent usage mode of the device). a.6 transmit messages considering the transmit data path, the full set of pci trans actions processed by the dma controller, per channel, is as follows:  read bd: cx28500 performs a burst read of 2 dwords from host memory. this transaction takes (3 + 2 + r) cycles during 32-bit mode, or (3 + 1 + r) cycles during 64-bit mode.  data transfer: frame information is read from host memory to cx28500 until either the end of the memory buffer, the end of the message, or the pci bus is lost. in the general case, this transaction takes (3 + x + r) cycles for 32-bit mode or (3 + [(x/2)] + r) cycles for 64-bit mode. where x is the number of dwords transferred. the largest value is the remaining length of the pci la tency timer or maxdata cycles. hence, the transaction may take (3 + maxdata + r).  write buffer status: this transaction takes (2 + 1 + w) cycles regardless of the 32- or 64-bit pci mode. a.7 allocation of internal slp buffer (fifo) space the total internal buffer space for slp usage is 32 kb in each direction?total of 64 kb full-duplex. in general, this memory should be allocated in ratio to the channels' bit rate. for example, one logical channel (unchannelized) working at 52 mbps should be allocated a buffer approximately five times the size of one logical channel working at 10 mbps. a.8 maximum feasible pci latency the maximum feasible pci latency for a given receive channel (max l pci-rx ) is defined as the maximum length of time in seconds that a receive channel must wait before the first data transaction is performed from its internal slp buffer. this can be considered as the amount of time required to service all the transmit channels plus the amount of time required to service all but one of the receive channels. this involves updating status and reading new buffer descriptors for all channels in both directions, transferring data from the host memory for all transmit channels, and transferring data to the host memory from the slp internal buffer for all but one of the receive channels.
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 170 mindspeed proprietary and confidential hence, max l pci-rx can be represented by the equations: or, where data is the maximum amount, in dwords, that can be transferred from a channel during one pci transaction. pci mode is the number of bits transferred by the pci in one clock. the maximum feasible pci latency for a given transmit channel (max l pci-tx ) is defined to be the maximum length of time in seconds that a transmit channel must wait until its first data transaction. this can be considered as the amount of time required to service all the receive channels plus the amount of time required to service all but one of the transmit channels. this involves updating status and reading new buffer descriptors for all channels in both directions, transferring data to the host memory for all receive channels, and transferring data from the host memory to the slp internal buffer for all but one of the transmit channels. hence max l pci-tx can be represented by the equations: or, where data is the maximum amount, in dwords, that can be transferred from a channel during one pci transaction. pci mode is the number of bits transferred by the pci in one clock. a.9 maximum endurable latency the maximum endurable latency of a channel (l ch ) is the amount of time that a specific channel can endure until the first data transaction. the timing of the endurable latency for a given receive channel (l ch-rx ) starts when that channel first requests dma service. the interval ends on the clock that the first dword of data is removed from the channel?s slp buffer by the dma for transferal to host memory, or at worst when its buffer is full. the timing of the endurable latency for a given transmit channel (l ch-tx ) starts when that channel first requests dma service (i.e., when the fifo empties to threshold level). the interval ends on the clock that the first dword of data is moved from host memory and is transferred to that channel?s slp buffer by the dma, or at worst when its buffer is empty. l ch-rx = (bufflen ? thr rx ) note: both of these maximum feasible pci latency tim es are internal latencies and do not include any external influences such as pci arbitration. 1 f pci ------- - 2 read bd read data 2 write status ? ++ ? () write data () numch 1 ? + numch ? ? ? ? ? ? 1 f pci ------- - 62 w 23 64 pci mode -------------------------- - ?? ?? r ++ ?? ?? ? + ? 3 data r ++++ ?? ?? 2 data w ++ () numch 1 ? + numch ? ? ? ? ? ? 1 f pci ------- - 2 read bd write data 2 write status ? ++ ? () read data () num ch 1 ? + numch ? ? ? ? ? ? 1 f pci ------- - 23 64 pcimode ------------------------ - ?? ?? r ++ ?? ?? 2 data 63 w ? ++ ++ ? ?? ?? 3 data r ++ () numch 1 ? + numch ? ? ? ? ? ? 1 f ch ------
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 171 mindspeed proprietary and confidential l ch-tx = * thr tx if endurable latency of a channel is less than maximum feasible pci latency in both the receive and transmit directions, no overflow or underflow occurs. a.10 pci bus utilization pci bus utilization is defined to be the ratio of the amount of time cx28500 uses the bus to the tota l amount of time that could be utilized by all components on the bus, including the host. utiliza tion is calculated by comparing the time required to transfer one bit of receive and one bit of transmit information across the pci and the time required to fill one bit of internal buffer space. the time required per bit to transfer across the pci (y bit ) is calculated as an average over one packet, by dividing the amount of time required for one packet?s transactions by the number of bits in the packet. giving the average time to transfer one bit: where p is packet length, measured in bits. hence y bit-rx can be represented by: z is the amount of data transferred in 32 pci cycles. roundup is a simple rounding up function. p is packet length in bits. pci mode is the number of bits transferred by one pci clock and thr is the fifo threshold for that channel. similarly for the transmit direction: where p is packet length, in bits. hence y bit-tx can be represented by: z is the amount of data transferred in 32 pci cycles. roundup is a simple rounding up function. p is packet length in bits. pci mode is the number of bits transferred by one pci clock, and thr is the fifo threshold for that channel. so the utilization, u, of the pc i bus due to one cx28500 is: 1 f ch ------ time for a bit of rx data 1 pf pci ? ----------------- read bd write packet data write status ++ {} = 1 pf pci ? ----------------- 3 w 3 64 pci mode -------------------------- - ?? ?? r ++ ?? ?? p pci mode -------------------------- - ?? ?? 2 w + () roundup p min th r z p ,, () () ---------------------------------------------- ?? ?? ?? ?? ? ++ + + ? ? ? ? ? ? time for a bit of tx data 1 pf pci ? ----------------- read bd read packet data write status ++ {} = 1 pf pci ? ----------------- 3 w 3 64 pci mode -------------------------- - ?? ?? r ++ ?? ?? p pci mode -------------------------- - ?? ?? 3 r + () roundup p min th r z p ,, () () ---------------------------------------------- ?? ?? ?? ?? ? ++ + + ? ? ? ? ? ? u amount time to transfer one bit across the pci amount time to transfer one bit of rx and tx in / out of cx 28500 () ------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------- - numch =
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 172 mindspeed proprietary and confidential a.11 maximum tolerable delay the filling of an slp buffer ca n be divided into 3 sections: 1. up to the point where the amount of data crosses the threshold; 2. the amount of data filled in max l pci ; 3. the amount of time left to fill the rest of the buffer. diagrammatically: spare  amount filled in max l pci  threshold data in the case of the receive di rection, the amount of time that an slp inte rnal buffer takes to fill the spare space in the buffer is the maximum tolerable delay. this time period is usable by the host (or other component) once per number of extra cycles it takes to completely empty the amount of data filled in that time. hence if the channel buffer is exactly in data equilibrium, this spare can only be used once until the same amount of cycles has been returned to cx28500. in the case of the transmit direction, the amount of time that an slp internal buffer takes to empty the spare space in the buffer is the maximum tolerable delay. this time period is usable by the host (or other component) once per number of extra cycles it takes to comple tely fill the amount of data emptied in that time. hence if the channel buffer is exactly in data equilibrium, this spare can only be used once until the same amou nt of cycles has been ?returned? to cx28500. the value of the maximum tolerable delay can be calculated and is represented by the following equation: a.12 other considerations 1. an overflow occurs if one of the following is false: a. utilization <1; b. l pci < l ch ; c. amount of data transferred > amount of data transferred in/out of the pci during l pci cx28500 during the same time 2. pci bus utilization allows an estimation of the numb er of cx28500 devices that can share one pci bus. however, the relationsh ip between utilization and the number of cx28500 devices is not linear. 3. the amount of data filled during the us age of spare cycles plus the amount of data already in the buffer can be used as the figure for the maximum allowable threshold. note: to avoid overflow or underflow of an internal slp buffer, u must be less than one and maximum feasible pci latency of each channel must be less than the maximum endurable latency of that channel. uy bit rx ? f ch rx ? ? y bit tx ? f ch tx ? ? + () numch = max l ch max l pci ?
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 173 mindspeed proprietary and confidential a.13 summary and explanation of terms used in calculations for each device configuration, there are three sets of standard variables and two sets of statistics. one of the statistics sets includes a calculation of spare time whic h takes into account the host using the maximum tolerable delay, and afterwards allowin g cx28500 to take the remain ing bus time to achieve 1 00% utilization. the second statistics set does not include spare ti me and indicates average utilization. below, as in the full breakdown of figures, the explanation is in 5 sections: 1. configuration?configurable variables; 2. suggested?configurable variables that have suggested values; 3. calculated?calculated variables common to both statistics sets; 4. including spare time?calculations include host /others usage of spare time; 5. not including spare time?calculations not including usage of spare time. table a-1. configuration variable name description calculated number of ch number of active channels configurable mem available (kb) memory available (kb) for all channels configurable packet length (bits) length of packet s, receive and transmit configurable ext. ch rate (kbps) channel rate of serial lines (pure) without taking into account the hdlc overhead configurable pci freq. (mhz) pci clock fr equency in mhz configurable read latency latency incurred by the pci due to a read transaction configurable write latency latency incurred by the pci due to a write transaction configurable pci bit mode number of bits tran sferred in one pci cycle configurable table a-2. suggestions variable name description calculated buffer len (bits) size of buffer available to each channel in eac h direction total of 32 bytes apportioned equally across number of channels rx threshold fifo threshold of rx channels set as half the buffer size tx threshold fifo threshold of tx channels set as half the buffer size table a-3. calculated (1 of 2) variable name description calculated int. ch rate (kbps)?rx actual rate at which the internal slp buffer fills taking into account hdlc framing and status bits. from actual channels rate, packet length and hdlc overhead. int. ch rate (kbps)?tx actual rate at which the internal slp buffer empties taking into account hdlc framing. from actual channels rate, packet length and hdlc overhead. pci freq (khz) frequency of the pci in khz. from configured pci frequency.
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 174 mindspeed proprietary and confidential time to read bd (average) average amo unt of time required to read a buffer descriptor. dependent on pci bit mode and the value of pci read latency. time to read bd (max) maximum amount of time required to read a buffer descriptor. dependent on pci bit mode and the value of pci read latency. time to update status number of pc i cycles required to update a packet status. dependent on pci write latency only. table a-4. including spare time variable name description calculated maxdata maximum amount of data that can be transferred across the pci to or from the internal slp buffer. calculated (by iteration) t aking into account amount filled in spare time, amount filled in while a channel waits to be serviced, and the channel?s threshold; separate for receive and transmit channels. max l ch (ms) rx maximum amount of time a channel can endure without a single data transaction before an overflow occurs. calculated from threshold, buffer length, and internal channel rate. max l pci (ms) rx maximum amount of ti me the dma will take from the end of spare time until the first data transaction from a specific channel. calculated (by iteration) t aking into account pci bit mode, pci bit rate, maxdata, and packet transactions of all channels. max l ch (ms) tx maximum amount of time a channel can wait without a single data transaction before its internal slp buffer is empty. calculated from threshold, buffer length, and internal channel rate. max l pci (ms) tx maximum amount of ti me the dma will take from the end of spare time until the fi rst data transaction to that channel. calculated (by iteration) t aking into account pci bit mode, pci bit rate, maxdata, and packet transactions of all channels. amount data filled in l pci rx amount of data in bits that is filled into the slp internal buffer during the maximum time the dma takes to service a specific channel with a data transaction. calculated from channel rate and l pci . amount data emptied in l pci tx amount of data in bits that is transferred from the slp internal buffer during the maximum time the dma takes to service a specific channe l with a data transaction. calculated from channel rate and l pci . spare time (rx/tx) amount of time the (rx/tx) fifo can endure before 100% pci bus utilization. calculated from l pci and l ch spare time (total) minimum spare ti me available after considering both rx/tx channels. ? in spare time amount filled/ emptied self explanatory. ? max total in slp maximum amount of data in slp internal buffers at any one time. calculated from buffer length, threshold, amount filled in spare time, and amount filled in l pci table a-3. calculated (2 of 2) variable name description calculated
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 175 mindspeed proprietary and confidential a.14 examples ta bl e s a - 6 through a-8 show calculated results for four different types of channel configuration. ta b l e s a - 6 and a-7 show similar results for three types of configuration, where all channels within each type are configured exactly the same, per the column heading. the only difference between ta b l e s a - 6 and a-7 is the read latency (r value), which increases from zero to two. this highlights the impact of a small increase in pci latency. ta b l e a - 8 gives results for a fourth system configuration that combines two differ ent channel configurations (t1 payload and overhead) operating simultaneously. since ta bl e s a - 6 through a-8 are calculated for only one cx28500 devi ce, total pci system utilization for a two- device system is approximately double what is shown on the following pages. a.15 differences in the combined t1 payload and overhead table refer to ta b l e s a - 6 through ta bl e s a - 8 . 1. memory available is apportioned according to the rate at which the bits arrive on that channel. hence a combination of high-speed channels and low-speed channels yields a different amount of buffering allocated to channels in the third example. table a-5. non ??spare time? calculations variable name description calculated maxdata maximum amount of data that can be transferred across the pci from the internal fifo. calculated (by iteration) t aking into account amount filled in while a channel waits to be serviced, and the channel?s threshold; separat e for receive and transmit channels. max l ch (ms) rx maximum amount of time a channel can endure without a single data transaction before an overflow will occur. calculated from threshold, buffer length, and internal channel rate. max l pci (ms) rx maximum amount of ti me the dma will take from the end of spare time until the first data transaction from a specific channel. calculated (by iteration) t aking into account pci bit mode, pci bit rate, maxdata, and packet transactions of all channels. max l ch (ms) tx maximum amount of time a channel can wait without a single data transaction before its internal slp buffer will be empty. calculated from threshold, buffer length, and internal channel rate. max l pci (ms) tx maximum amount of ti me the dma will take from the end of spare time until the fi rst data transaction to that channel. calculated (by iteration) t aking into account pci bit mode, pci bit rate, maxdata, and packet transactions of all channels. utilization?rx average ratio of host to cx28500 rx utilization of the pci. amount of time taken to transf er one bit of rx data out of cx28500 divided by the amount of time to transfer one bit of receive data to the host memory. utilization?total average ratio of host to cx28500 utilizati on of the pci. cx28500 receive utilization plus cx28500 transmit utilization. amnt data filled in l pci-rx rx amount of data added to receive internal slp buffers during the maximum amount of time taken to reach it. calculated from internal channel rate and l pci . amnt data filled in l pci-tx tx amount of data removed from transmit internal slp buffers during the maximum amount of time taken to reach it. calculated from internal channel rate and l pci .
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 176 mindspeed proprietary and confidential 2. throughout the calculation, each column relates only to that specific set of channels with one exception. the utilization abs total represents the ov erall utilization of the cx28500. table a-6. example one (1 of 2) 66 mhz pci 44-byte messages 12-byte messages 168 x 1536k channels 6 x 44.21m channels 168 x 4k channels configuration 64-bit pci 32-bit pci 64-bit pci 32-bit pci 64-bit pci 32-bit pci number of ch n 168 168 6 6 168 168 mem available (kb) m 64 64 64 64 64 64 packet length (bits) p 352 352 352 352 96 96 ext. ch rate (kbps) r 1536 1536 44210 44210 4 4 pci freq. (mhz) fpci 66 66 66 66 66 66 read latency r000000 write latency w000000 pci bit mode pbit 64 32 64 32 64 32 suggested buffer size bufflen 1592 1592 43723 43723 1592 1592 rx threshold thr ? rx 796 796 21861 21861 796 796 tx threshold thr ? tx 796 796 21861 21861 796 796 calculated int. ch rate (kbps) fch ? rx 1568.68 1568.68 45150.64 45150.64 4.27 4.27 int. ch rate (kbps) fch ? tx 1437.96 1437.96 41388.09 41388.09 3.20 3.20 pci freq. (khz) fpci 66000 66000 66000 66000 66000 66000 time to read bd average 4 5 4 5 4 5 time to read bd actual454545 time to update status ?333333 including spare time maxdata rx 352 352 352 352 96 96 maxdata tx 352 352 352 352 96 96 max l ch (ms) rx 0.508 0.508 0.484 0.484 186.607 186.607 max l pci (ms) rx 0.076 0.109 0.003 0.004 0.056 0.069 max l ch (ms) tx 0.554 0.554 0.528 0.528 248.810 248.810 max l pci (ms) tx 0.076 0.109 0.003 0.004 0.056 0.069 amnt data filled in l pci rx 120 171 118 168 0 0 amnt data emptied on l pci tx 110 157 108 153 0 0 spare time (ms) rx 0.431 0.398 0.482 0.480 186.551 186.538 spare time (ms) tx 0.477 0.444 0.526 0.525 248.754 248.741
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 177 mindspeed proprietary and confidential spare time (ms) total 0.431 0.398 0.482 0.480 186.551 186.538 spare time (cycles) total 28466 26287 31783 31711 12312378 12311540 in spare time amnt filled rx 677 625 21743 21694 796 796 in spare time amnt emptied tx 620 573 19931 19886 597 597 max total in slp buffer rx 1592 1592 43723 43723 1592 1592 max total in slp buffer tx 1526 1526 41900 41900 1393 1393 not including spare time maxdata rx 352 352 352 352 96 96 maxdata tx 352 352 352 352 96 96 max l ch (ms) rx 0.508 0.508 0.484 0.484 186.607 186.607 max l pci (ms) rx 0.076 0.109 0.003 0.004 0.056 0.069 max l ch (ms) tx 0.554 0.554 0.528 0.528 248.810 248.810 max l pci (ms) tx 0.076 0.109 0.003 0.004 0.056 0.069 utilization rx 0.170 0.238 0.175 0.245 0.001 0.001 utilization tx 0.156 0.218 0.160 0.224 0.001 0.001 utilization total 0.326 0.457 0.335 0.469 0.002 0.003 amnt data filled in l pci rx 120 171 118 168 0 0 amnt data emptied in l pci tx 110 157 108 153 0 0 table a-7. example two (1 of 3) 66 mhz pci 44-byte messages 12-byte messages 168 x 1536k channels 6 x 44.21m channels 168 x 4k channels configuration 64-bit pci 32-bit pci 64-bit pci 32-bit pci 64-bit pci 32-bit pci number of ch n 168 168 6 6 168 168 mem available (kb) m 64 64 64 64 64 64 packet length (bits) p 352 352 352 352 96 96 ext. ch rate (kbps) r 1536 1536 44210 44210 4 4 pci freq. (mhz) fpci 66 66 66 66 66 66 read latency r222222 write latency w000000 pci bit mode pbit 64 32 64 32 64 32 suggested table a-6. example one (2 of 2) 66 mhz pci 44-byte messages 12-byte messages 168 x 1536k channels 6 x 44.21m channels 168 x 4k channels configuration 64-bit pci 32-bit pci 64-bit pci 32-bit pci 64-bit pci 32-bit pci
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 178 mindspeed proprietary and confidential buffer size bufflen 1592 1592 43723 43723 1592 1592 rx threshold thr ? rx 796 796 21861 21861 796 796 tx threshold thr ? tx 796 796 21861 21861 796 796 calculated int. ch rate (kbps) fch ? rx 1568.68 1568.68 45150.64 45150.64 4.27 4.27 int. ch rate (kbps) fch ? tx 1437.96 1437.96 41388.09 41388.09 3.20 3.20 pci freq. (khz) fpci 66000 66000 66000 66000 66000 66000 time to read bd average 6 7 6 7 6 7 time to read bd actual676767 time to update status ?333333 including spare time maxdata rx 352 352 352 352 96 96 maxdata tx 352 352 352 352 96 96 max l ch (ms) rx 0.508 0.508 0.484 0.484 186.607 186.607 max l pci (ms) rx 0.092 0.125 0.003 0.004 0.071 0.084 max l ch (ms) tx 0.554 0.554 0.528 0.528 248.810 248.810 max l pci (ms) tx 0.091 0.124 0.003 0.004 0.071 0.084 amnt data filled in l pci rx 144 195 143 192 0 0 amnt data emptied in l pci tx 132 179 129 174 0 0 spare time (ms) rx 0.416 0.383 0.481 0.480 186.536 186.523 spare time (ms) tx 0.462 0.429 0.525 0.524 248.738 248.726 spare time (ms) total 0.416 0.383 0.481 0.480 186.536 186.523 spare time (cycles) total 27458 25279 31747 31675 12311370 12310532 in spare time amnt filled rx 653 601 21719 21669 796 796 in spare time amnt emptied tx 598 551 19909 19863 597 597 max total in slp buffer rx 1592 1592 43723 43723 1592 1592 max total in slp buffer tx 1526 1526 41899 41899 1393 1393 not including spare time maxdata rx 352 352 352 352 96 96 maxdata tx 352 352 352 352 96 96 max l ch (ms) rx 0.508 0.508 0.484 0.484 186.607 186.607 max l pci (ms) rx 0.092 0.125 0.003 0.004 0.071 0.084 max l ch (ms) tx 0.554 0.554 0.528 0.528 248.810 248.810 table a-7. example two (2 of 3) 66 mhz pci 44-byte messages 12-byte messages 168 x 1536k channels 6 x 44.21m channels 168 x 4k channels configuration 64-bit pci 32-bit pci 64-bit pci 32-bit pci 64-bit pci 32-bit pci
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 179 mindspeed proprietary and confidential max l pci (ms) tx 0.091 0.124 0.003 0.004 0.071 0.084 utilization rx 0.193 0.261 0.198 0.268 0.001 0.002 utilization tx 0.177 0.239 0.182 0.246 0.001 0.001 utilization total 0.370 0.500 0.380 0.514 0.003 0.003 amnt data filled in rx 144 195 143 192 0 0 amnt data emptied in l pci tx 132 179 129 174 0 0 table a-7. example two (3 of 3) 66 mhz pci 44-byte messages 12-byte messages 168 x 1536k channels 6 x 44.21m channels 168 x 4k channels configuration 64-bit pci 32-bit pci 64-bit pci 32-bit pci 64-bit pci 32-bit pci
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 180 mindspeed proprietary and confidential table a-8. example three (1 of 2) 66 mhz pci 44-byte messages 12-byte messages 168 x 1536k channels 6 x 44.21m channels 168 x 4k channels configuration 64-bit pci 32-bit pci 64-bit pci 32-bit pci 64-bit pci 32-bit pci number of ch n 168 168 ? ? ? ? total mem available (kb) ? 64 64 ? ? ? ? mem available (kb) m 63.83 0.17 ? ? ? ? packet length (bits) r 352 96 ? ? ? ? ext. ch rate (kbps) r 1536 4 ? ? ? ? pci freq. (mhz) fpci 66 66 ? ? ? ? read latency r 0 0 ? ? ? ? write latency w 0 0 ? ? ? ? pci bit mode pbit 64 64 ? ? ? ? suggested buffer size bufflen 1588 36 ? ? ? ? rx threshold thr ? rx 794 18 ? ? ? ? tx threshold thr ? tx 794 18 ? ? ? ? calculated int. ch rate (kbps) fch ? rx 1569 4 ? ? ? ? int. ch rate (kbps) fch ? tx 1438 3 ? ? ? ? pci freq. (khz) fpci 66000 66000 ? ? ? ? time to read bd average 4 4 ? ? ? ? time to read bd actual 4 4 ? ? ? ? time to update status ? 3 3 ? ? ? ? including spare time maxdata rx 352 0 ? ? ? ? maxdata tx 352 0 ? ? ? ? max l ch (ms) rx 0.506 4.219 ? ? ? ? max l pci (ms) rx 0.125 0.125 ? ? ? ? max l ch (ms) tx 0.552 0.625 ? ? ? ? max l pci (ms) tx 0.125 0.125 ? ? ? ? amnt data filled in l pci rx 195 1 ? ? ? ? amnt data emptied in l pci tx 179 0 ? ? ? ? spare time (ms) rx 0.382 4.094 ? ? ? ? spare time (ms) tx 0.428 5.500 ? ? ? ? spare time (ms) total 0.382 0.382 ? ? ? ? spare time (cycles) total 25181 25181 ? ? ? ?
cx28500 pci bus latency and utilization analysis 28500-DSH-002-C mindspeed technologies ? 181 mindspeed proprietary and confidential in spare time amnt filled rx 599 2 ? ? ? ? in spare time amnt emptied tx 549 1 ? ? ? ? max total in slp buffer rx 1588 20 ? ? ? ? max total in slp buffer tx 1522 20 ? ? ? ? not including spare time maxdata rx 352 18 ? ? ? ? maxdata tx 352 18 ? ? ? ? max l ch (ms) rx 0.506 4.219 ? ? ? ? max l pci (ms) rx 0.126 0.126 ? ? ? ? max l ch (ms) tx 0.552 5.625 ? ? ? ? max l pci (ms) tx 0.126 0.126 ? ? ? ? utilization rx 0.170 0.002 ? ? ? ? utilization tx 0.156 0.002 ? ? ? ? utilization total 0.326 0.004 ? ? ? ? utilization abs total 0.330????? amnt data filled in l pci rx 198 1 ? ? ? ? amnt data emptied in l pci tx 181 0 ? ? ? ? table a-8. example three (2 of 2) 66 mhz pci 44-byte messages 12-byte messages 168 x 1536k channels 6 x 44.21m channels 168 x 4k channels configuration 64-bit pci 32-bit pci 64-bit pci 32-bit pci 64-bit pci 32-bit pci
28500-DSH-002-C mindspeed technologies ? 182 mindspeed proprietary and confidential appendix b: example of an arbitration for fast back-to-back and non-fast back-to-back transactions figure b-1 illustrates, in a specific scenar io, cx28500?s pci transactions while operating as a master and fast back-to-back feature enabled. cx28500 performs as a master while operating at 64-bit address-data, a burst write of 4 dwords, which are transferred during the first cycle and a burst write of 6 dwords which are transferred during the second cycle. it is seen that both transaction cycles require 4 pclk cycles. figure b-1. pci burst write: two 64-bit fast back-to-back transactions to same target address data1 data3 address data1 data3 data5 data2 data4 data2 data4 data6 bus cmd be1 be3 bus cmd be1 be3 be5 be2 be4 be2 be4 be6 500052_040 clk frame# req64# ad[31:0] ad[63:32] c/be#[3:0] c/be#[7:4] par par64 irdy# trdy# devsel# ack64# general note: 1. bex means byte enable, where x is a numerical value between 1 and 8. for example, be1 means byte one is enabled.
example of an arbitration for fast back-to-back and non-fast back-to- back transactions 28500-DSH-002-C mindspeed technologies ? 183 mindspeed proprietary and confidential figure b-2 illustrates, in a specific configur ation, cx28500?s pci transactions wh ile operating as a master, and fast back-to-back feature enabled. cx28500 performs as a master while operating at 32-bit address-data, a burst write of 2 dwords, which are transferred during the first cycle and a burst write of 3 dwords, which are transferred during the second cycle. both transaction cycles require 4 pclk cycles. figure b-2. pci burst write: two 32-bit fast back-to-back transactions to same target clk frame# req64# ad[31:0] ad[63:32] c/be#[3:0] c/be#[7:4] par par64 irdy# trdy# devsel# ack64# address data1 address data1 data3 data2 data2 bus cmd be1 bus cmd be1 be3 be2 be2 500052_041 general note: 1. bex means byte enable, where x is a numerical value between 1 and 8. for example, be1 means byte one is enabled.
example of an arbitration for fast back-to-back and non-fast back-to- back transactions 28500-DSH-002-C mindspeed technologies ? 184 mindspeed proprietary and confidential figure b-3 illustrates how cx28500 operates at 64-bit address-data and perf orms a burst read of 4 dwords followed by a burst read of 6 dwords. the fast back-to-back is disabled. it can be observed that the first cycle takes 5 pclk cycles (with one pclk post-data phase) and the second cycle of transferring 6 dwords requires 6 pclk cycles. figure b-3. pci burst read: two 64-bit transactions address data1 data3 address data1 data3 data5 data2 data4 data2 data4 data6 bus cmd bus cmd be1 be2 be3 be1 be3 be5 be4 be2 be4 be6 500052_042 clk frame# req64# ad[31:0] ad[63:32] c/be#[3:0] c/be#[7:4] par par64 irdy# trdy# devsel# ack64# general note: 1. bex means byte enable, where x is a numerical value between 1 and 8. for example, be1 means byte one is enabled.
example of an arbitration for fast back-to-back and non-fast back-to- back transactions 28500-DSH-002-C mindspeed technologies ? 185 mindspeed proprietary and confidential figure b-4 illustrates how cx28500 operates at 32-bit address-data and performs a burst read of 2 dwords transfer during the first cycle and 3 dwords transfer during the second cycle. the fast back-to-back feature is disabled. it can be observed that the first cycle takes 5 pclk cycles (with one pclk post-data phase) and the second cycle of transferring 3 dwords requires 6 pclk cycles. figure b-4. pci burst: two 32-bit transactions clk frame# req64# ad[31:0] ad[63:32] c/be#[3:0] c/be#[7:4] par par64 irdy# trdy# devsel# ack64# address data1 address data1 data3 data2 data2 bus cmd bus cmd be1 be1 be3 be2 be2 500052_045 general note: 1. bex means byte enable, where x is a numerical value between 1 and 8. for example, be1 means byte one is enabled.
example of an arbitration for fast back-to-back and non-fast back-to- back transactions 28500-DSH-002-C mindspeed technologies ? 186 mindspeed proprietary and confidential in figure b-5 , cx28500 performs pci transactions as a master while fast back-to-back enabled and it operates at 64-bit address-data. a burst write of 4 dwords are transferred during the first cycle and a burst read of 6 dwords are transferred during the second cycle. it can be observed that the first cycle requires 3 pclk cycles and the second cycle requires 6 pclk cycles. figure b-5. pci burst write followed by burst read: fast back-to-back to same target clk frame# req64# ad[31:0] ad[63:32] c/be#[3:0] c/be#[7:4] par par64 irdy# trdy# devsel# ack64# address data1 data3 address data1 data3 data5 data2 data4 data2 data4 data6 bus cmd bus cmd be1 be2 be3 be1 be3 be5 be4 be2 be4 be6 500052_043 general note: 1. bex means byte enable, where x is a numerical value between 1 and 8. for example, be1 means byte one is enabled.
example of an arbitration for fast back-to-back and non-fast back-to- back transactions 28500-DSH-002-C mindspeed technologies ? 187 mindspeed proprietary and confidential in figure b-6 , cx28500 operates at 64-bit address-data and performs a burst read of 4 dwords followed by a burst write of 6 dwords. the fast back-to-back is disabled. it can be observed that the first cycle requires 3 pclk cycles and the second cycle requires 6 pclk cycles. figure b-6. pci burst read followed by burst write clk frame# req64# ad[31:0] ad[63:32] c/be#[3:0] c/be#[7:4] par par64 irdy# trdy# devsel# ack64# address data1 data3 address data1 data3 data5 data2 data4 data2 data4 data6 bus cmd bus cmd be1 be2 be3 be1 be3 be5 be4 be2 be4 be6 500052_044 general note: 1. bex means byte enable, where x is a numerical value between 1 and 8. for example, be1 means byte one is enabled.
28500-DSH-002-C mindspeed technologies ? 188 mindspeed proprietary and confidential appendix c: t3 frame relay switch application this appendix illustrates the detailed description of the cx2833x, cx2834x , and cx28500 devi ce communications. figure c-1. high-end router application cx28333 cx28333 liu liu cx28343 t3 framer cx28343 t3 framer cx28500 shared memory cpu b r i d g e pci t3/e3 t3/e3 t3/e3 t3/e3 t3/e3 t3/e3 port 0 port 1 port 2 port 3 port 4 port 5 port 6 port 7 port 8 port 9 port 10 port 11 port 12 port 13 port 14 port 15 optional local mpu mem ebus 6 ports t3/e3 overhead (tdl) see figure c-4, t3/e3 framer connection with hdlc controller (t3/e3 overhead path) 6 ports t3/e3 payload (tdl) see figure c-3, t3/e3 framer connection with hdlc controller (t3/e3 payload path) system bus see figure c-2, ds3/e3 line unit interface connection with t3/e3 framer coax (typ) 500052_075
t3 frame relay switch application 28500-DSH-002-C mindspeed technologies ? 189 mindspeed proprietary and confidential figure c-2. ds3/e3 line unit inte rface connection with t3/e3 framer rclk recovered clock for each channel receiver, intended for storing the corresponding rdat* into the following framer or logic. rclk transmit bit clock input for storing with transmit data. rpos resynchronized review data intended to store in the corresponding rclk*. tpos synchronized transmit data intended to store in the corresponding tclk*. (for details see cx28332/cx28333 data sheet.) figure c-3. t3/e3 framer connection with hdlc controller (t3/e3 payload path) rclk rpos rneg tclk tpos tneg rclk rpos rneg tclk tpos tneg cx2833x cx2834x 500052_076 rxgapck rdat rsync txgapck tdat tsync rclk rdat rsync tclk tdat tsync roof cx2834x cx28500 t3/e3 payload 500052_003b
t3 frame relay switch application 28500-DSH-002-C mindspeed technologies ? 190 mindspeed proprietary and confidential tsync, rsync as3 frame synchronization specification tdat/rdat ds3/e3 transmits receive data rxgapc transmit, receive clock txgapck (for details see cx28313 asic specification.) figure c-4. t3/e3 framer connection with hdlc controller (t3/e3 overhead path) tsync, rsync as3 frame synchronization specification tdat/rdat ds3/e3 transmits receive data rxgapck transmit, receive clock txgapck (for details see cx28313 asic specification.) rextck rext rsync textck text rclk rdat rsync tclk tdat tsync roof cx2834x cx28500 t3/e3 overhead 500052_003c
28500-DSH-002-C mindspeed technologies ? 191 mindspeed proprietary and confidential appendix d: example of little-big endian byte ordering an example of little-big-endian byte ordering is shown in the next table. for the example a 32-bit dword was used?76543210h: table d-1. little endian address x+3 x+2 x+1 x data 76h 54h 32h 10h table d-2. big endian address x+3 x+2 x+1 x data 10h 32h 54h 76h note: when little-big-endian byte ordering is used, this only refers to the data portion of the interface to the host, meaning that only data tr ansfers are affected. this is useful mainly for applications that use 32 -bit values, rather than fo r plain stream applications. using big-endian mode in combination with buffers that are not 32 -bit aligned is not recommended.
28500-DSH-002-C mindspeed technologies ? 192 mindspeed proprietary and confidential appendix e: tsbus e.1 connection between cx28500 and other tsbus device this section details the signals required to implement the tsbus 1 interface. the cx28500 implements a subset of this bus. figure e-1 illustrates the tsbus connections between the other device and cx28500. the signals required are summarized in ta b l e s e - 1 and e-2 . the tsbus consists of the payload and the overhead bus. each bus has a transmit and receive path. the receive path is defined from the other device to cx28500, and the transmit path is defined from cx28500 to the other device. note that while the bus defines the tsb_rsynci, tsb_tsynci and tsb_tsynco pins, these are absent from the cx28500, and thus a cx28500 implements only a subset of the tsbus standard. see the documentation of the cx29503 or cx28560 parts for more complete explanation of the tsbus standard. figure e-1 illustrates the cx28500 pin definitions in tsbus mode. 1.time slot bus
tsbus 28500-DSH-002-C mindspeed technologies ? 193 mindspeed proprietary and confidential figure e-1. cx28500 time slot interface pins table e-1. system side interface: payload time slot bus (1 of 2) symbol reset behavior i/o definition tsb_clk low in payload time slot bus clock: this clock is usually based on sib_txhsclk 1 . it is used for all timing on the payload time slot bus. clock rate is 51.84 mhz ( 20 ppm) tsb_stb low in payload time slot bus strobe: a strobe sign al that indicates the start of a frame with 84 time slots carrying payload data. the strobe indicates th e beginning of each p ayload time slot frame. tsb_tdat ? out payload time slot bus transmit data: this is the serial payload data sent from the cx28500 to the other device. this signal may be driven on the rising edge of tsb_clk or on the falling edge, according to the tdat_edge bit in the tsiu port config uration register. 1 this is a signal that is output from a cx29610, and is used by the cx29503 as a reference 51.84mhz clock. when cx29610 is not used, it may be derived from another reference clock. tbus device cx28500 payload overhead payload overhead tsb_clk tsb_tstuff tsb_tdat tsb_rstuff tsb_rdat tsb_stb tsb_tsynco tsb_tsynci tsb_rsync tsb_oclk tsb_otstuff tsb_otdat tsb_orstuff tsb_ordat tsb_ostb tsb_tclk tsb_tstuff tsb_tdat tsb_rclk tsb_rstuff tsb_rdat tsb_stb tsb_tclk tsb_tstuff tsb_tdat tsb_rclk tsb_rstuff tsb_rdat tsb_stb 51.84 mhz 12.96 mhz 500052_077 tsb_tsynco tsb_tsynci tsb_rsync
tsbus 28500-DSH-002-C mindspeed technologies ? 194 mindspeed proprietary and confidential tsb_tstuff high in payload time slot bus transmit stuff indication: when high, indicates a stuff byte must be transmitted in place of the data byte arriving 8 time slots later. tsb_rdat low in payload time slot bus receive data: this is the received serial payload data. it may be sampled on the rising edge of tsb_clk or on the falling edge, according to the rdat_edge bit in the rsiu port config uration register. tsb_rstuff high in payload time slot bus receive stuff indi cation: when high, indicates that data on tsb_rdat is not valid data. tsb_rdat is stuffed with all 1s. table e-2. system side interface: overhead time slot bus symbol reset behavior i/o definition tsb_oclk low in overhead time slot bus clock: this clock is based on sib_txhsclk 1 . it is used for all timing on the overhead time slot bus. clock rate is 12.96 / 11.184 / 8.592 mhz. tsb_ostb low in overhead time slot bus strobe: a strobe si gnal that indicates the star t of a frame with 84 time slots carrying overhead data. th e strobe indicates the beginnin g of each overhead time slot frame. tsb_otdat ? out overhead time slot bus transmit data: this is the serial overhead data sent from the cx28500 to the other device. this signal may be driven on the rising edge of tsb_oclk or on the falling edge, according to the tdat_edge bit in the tsiu port configuration register. tsb_otstuff high in overhead time slot bus transmit stuff indication: when high, indicates a stuff byte must be transmitted in place of the data byte arriving 8 time slots later. tsb_ordat low in overhead time slot bus receive data: this is the received serial overhead data. it may be sampled on the rising edge of tsb_oclk or on the falling edge, according to the rdat_edge bit in the rsiu port configuration register. tsb_orstuff high in overhead time slot bus receive stuff i ndication: when high, indicates that data on tsb_rdat is not valid data. tsb_rdat is stuffed with all 1s. 1 this is a signal that is output from a cx29610, and is used by the cx29503 as a refe rence 51.84mhz clock. when cx29610 is not used, it may be derived fr om another re ference clock. table e-1. system side interface: payload time slot bus (2 of 2) symbol reset behavior i/o definition 1 this is a signal that is output from a cx29610, and is used by the cx29503 as a reference 51.84mhz clock. when cx29610 is not used, it may be derived from another reference clock.
tsbus 28500-DSH-002-C mindspeed technologies ? 195 mindspeed proprietary and confidential figure e-2. source/destination of tsbus block line-side signals table e-3. system side interface: overhead time slot bus frame (1 of 2) tsbus source/destination overhead data communication channel mapped to virtual serial port (vsp) description data rate ds1/e1 framer no. 1-28 f-bit data link/sa4 bit data link 112 kbps sts-12/sts-3/stm-1 mapper regenerator section data communication channel (dccr) bytes 1?3 194 kbps sts-12/sts-3/stm-1 mapper multiplex section (lin e) data communication channel (dccm) byte 1?9 583 kbps sonet/sdh sts-1/au-3 mapper path user channel: f2 64 kbps sonet/sdh sts-1/au-3 mapper path user channel: f3 64 kbps electrical e3 electrical ds3 sonet sts-1 spe sonet sts-1 spe sonet sts-1 spe sonet sts-1 spe sdh au-3 sdh au-3 tsbus tsbus tsbus tsbus tsbus/ e1 framer tsbus/ e1 framer tsbus (c-11)/ ds1 framer tsbus (c-12)/ e1 framer e3 e2 e1 14 416 17 428 17 4 74 28 28 7321 7321 7428 17 321 ds3 ds2 ds1 ds3 ds2 ds1 ds3 ds2 ds1 vtg vt1.5 vtg vt2.0 tug-2 tu-11 tug-2 tu-12 500052_031
tsbus 28500-DSH-002-C mindspeed technologies ? 196 mindspeed proprietary and confidential e.1.1 vsp mapping of intermix ed digital level 2 signals the information in this subsection relates to the way a cx29503 device presents channels of various types of mappings to the cx28500 on the tsbus. it is reproduced from the cx29503 datasheet in order to make the explanation of the timeslot assignments complete. the following digital level 2 signals can transport either ds 1 or e1 signals: vtg, tug-2, and ds2. sonet, sdh, and pdh transport their respective level 2 signals in sets of seven level 2 signals. this set of seven level 2 signals can operate in mixed mode where a portion of the seven level 2 multiplexed signals transport ds1 signals and the remainder transport e1 signals. any given level 2 signal in mixed mode can only transport ds1 signals or e1 signals. it cannot transport both signals. ta bl e e - 4 defines the mapping of ds1 and e1 signals when they are extracted from a mixed set of seven vtg?s, a mixed set of seven tug-2s, or a mixed set of seven ds2s. each level 2 signal has a set of 3 or 4 related framers. all framers within a set must be configured for the same type of signal. this prevents framers for different data paths from multiplexing data into the same time slot. there are four framers in a set for ds1, vt1.5, and vc-11 signals. there are three framers in a set for e1, vt2.0, and vc-12 signals. the types of level 2 signals that can be mixed together are limited to the following combinations: 1. ds2 signals containing ds1 signals and the ds2 signals containing e1 signals. 2. vtg signals containing vt1.5, which contain ds1 signal s and vtg signals containing vt2.0, which contain e1 signals. 3. tug-2 signals containing vc-11, which contain ds1 signals and vtg-2 signals containing vc-12, which contain e1 signals. sonet/sdh sts-1/au-3 mapper spe/au path overhead nibble n1 (4 lsbs) path data channel/bit oriented or lapd tandem connection 32 kbps unused communication time slots future use 3.564 mbps command status processor (csp) csp channel. u sed to control/monitor cx29503 device. 6.48 mbps table e-4. vsp mapping of intermixe d digital level 2 signals contai ning either ds1 or e1 signals (1 of 2) framer set no. framer no. concatenated time slot numbers vsp no. framer configured to extract ds1 signal framer configured to extract e1 signal 1 1 1, 29, 57 1, 22, 43 64 1 2 2 2, 30, 58 2, 23, 44, 65 2 3 3 3, 31, 59 3, 24, 45, 66 3 4 4 4, 32, 60 4, 25, 46, 67 4 5 5 5, 33, 61 5, 26, 47, 68 5 table e-3. system side interface: overhead time slot bus frame (2 of 2) tsbus source/destination overhead data communication channel mapped to virtual serial port (vsp) description data rate
tsbus 28500-DSH-002-C mindspeed technologies ? 197 mindspeed proprietary and confidential e.2 timing details e.2.1 payload bus, ac characteristics the cx28500 (hdlc controller) device operates as the slave on the time-slot bus, and the other device (usually cx29503) is the master. the master generates tsbus clocks and control signals and the cx28500 device responds by transmitting data to or receiving data from the master device. the master generates a tsbus frame strobe (tsb_stb) on the rising edge of tsb_clk. the ti me slot bus frame strobe tsb_stb indicates the start of an n time slot frame carrying payload data, where the standard value of n is 84 (but this is configurable). 6 6 6, 34, 62 6, 27, 48, 69 6 7 7 7, 35, 63 7, 28, 49, 70 7 1 8 8, 36, 64 8, 29, 50, 71 8 2 9 9, 37, 65 9, 30, 51, 72 9 3 10 10, 38, 66 10, 31, 52, 73 10 4 11 11, 39, 67 11, 32, 53, 74 11 5 12 12, 40, 68 12, 33, 54, 75 12 6 13 13, 41, 69 13, 34, 55, 76 13 7 14 14, 42, 70 14, 35, 56, 77 14 1 15 15, 43, 71 15, 37, 57, 78 15 2 16 16, 44, 72 16, 37, 58, 79 16 3 17 17, 45, 73 17, 38, 59, 80 17 4 18 18, 46, 74 18, 39, 60, 81 18 5 19 19, 47, 75 19, 40, 61, 82 19 6 20 20, 48, 76 20, 41, 62, 83 20 7 21 21, 49, 77 21, 42, 63, 84 21 1 22 22, 50, 78 na 22 2 23 23, 51, 79 na 23 3 24 24, 52, 80 na 24 4 25 25, 53, 81 na 25 5 26 26, 54, 82 na 26 6 27 27, 55, 83 na 27 7 28 28, 56, 84 na 28 general note: framers with the same set number must be configured for the same data signal (i.e., all framers within a set must be configured for ds1 or e1 signals but not both). table e-4. vsp mapping of intermixe d digital level 2 signals contai ning either ds1 or e1 signals (2 of 2) framer set no. framer no. concatenated time slot numbers vsp no. framer configured to extract ds1 signal framer configured to extract e1 signal
tsbus 28500-DSH-002-C mindspeed technologies ? 198 mindspeed proprietary and confidential the time slot bus exchanges data over two i/o chip boundaries so care must be taken in ensuring that the data is exchanged on the right phase of the master tsbus clock tsb_clk. a possible solution for ensuring correct data exchange is for the slave (cx28500) to transmit data on the rising edge of tsb_clk, and sample the received data on the falling edge of tsb_clk. there is only one time slot frame strobe used (tsb_stb) for transmit and receive direction. there is also only one clock (tsb_clk) used in the definition of bit boundaries for transmit and receive. this results in the time slot frame alignment of the receive and transmit payload (illustrated in figure e-3 ). each time slot in the time slot bus consists of eight serial data bits. the msb bit for each time slot is transmitted first. e.2.2 transmit timing the master generates clock, frame sy nc strobe signal, and stuf f signal. cx28500 will g enerate transmit data (tsb_tdat) or generate an all-1s stuff pattern eight ti me slots after receiving an active stuff signal (tsb_tstuff). the master will generate a frame sync strobe (tsb_stb) out put synchronously with the rising edge of tsb_clk. figure e-3 illustrates the timing requirements for the transmit. figure e-4 illustrates the transmit stuff signal (tsb_tstuff). th e timing values are illustrated in ta bl e e - 4 , but see section 10.2.5 serial interface timing and switching characteristics. figure e-3. payload time slot bus transmit data (tsb_tdat) tsb_clk tsb_tdat transmit bit n transmit bit n+1 transmit bit n+2 t per t pwh t pwl t s t h 500052_033
tsbus 28500-DSH-002-C mindspeed technologies ? 199 mindspeed proprietary and confidential e.2.3 receive timing the master generates clock, data, frame sync strobe signal, and the stuff signal (tsb_rstuff). the master generates an all ones stuff pattern in place of the payload data during the same time slot that the receive stuff signal (tsb_rstuff) is active. the master generates control and data outputs synchronously with the rising edge of tsb_clk. the nominal clock frequency is 51.84 mhz. figure e-5 shows the timing requirements for the receive figure e-4. payload time slot bus transmit stuff indicator (tsb_tstuff) table e-5. transmit timing values label description min max unit t fc clock frequency t dc /52 mhz t dc /52 mhz ns t dc duty cycle 40% 60% ? t s setup, tsb_tdat to rising edge of tsb_clk 15 (1) 2 (2) ?ns t h hold, tsb_tdat from rising edge of tsb_clk 15 (1) 3 (2) ?ns footnote: (1) if port frequency is less than 13 mhz. (2) if port frequency is more than 13 mhz. tsb_clk tsb_tstuff tsb_tdat bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 msb lsb time slot #n (8 bits of serial data) byte 1 byte 2 byte 3 byte 4 byte 5 byte 7 byte 6 byte 8 stuffed time slot the byte arriving 8 time slots (bytes) after tsb_stuff is expected to be stuffed 500052_034
tsbus 28500-DSH-002-C mindspeed technologies ? 200 mindspeed proprietary and confidential interface. see figure e-6 for the receive stuff signal (tsb_rstuf f). the timing values are illustrated in ta bl e e - 5 , but see section 10.2.5 serial interface timing and switching characteristics. figure e-5. payload time slot bus receive data (tsb_rdat) figure e-6. payload time slot bus receive stuff indicator (tsb_rstuff) tsb_clk tsb_rdat receive bit n receive bit n+1 receive bit n+2 t per t pwh t pwl 500052_035 tsb_clk tsb_rstuff tsb_rdat bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 msb lsb time slot #n (8 bits of serial data) stuffed time slot the byte arriving with the tsb_tstuff is stuffed and contains no real data 500052_036
tsbus 28500-DSH-002-C mindspeed technologies ? 201 mindspeed proprietary and confidential e.3 overhead bus, ac characteristics the overhead tsbus has the same operation as the payloa d tsbus. the only difference is that the tsb_oclk clock can be run at 12.96/11.184/8.592 mhz compared to the payload tsbus frequency of 51.84 mhz. e.3.1 transmit timing see section e.2.2 . e.3.2 receive timing see section e.2.3 . e.4 dc characteristics see chapter 10.0 of this document.
28500-DSH-002-C mindspeed technologies ? 202 mindspeed proprietary and confidential appendix f: notation, acronyms, abbreviations, and definitions this appendix serves as a reference regarding nota tional conventions used throughout the specification. f.1 radix notation the general representation for numbers is as follows: the suffix is often dropped for clarity when the context makes the intended radix obvious. note that this suffix convention requires that letters [abcdef] used in hex numbers always be capitalized. f.2 bit stream convention by historical convention, digital voice data represented in octet samples are transmitted serially starting at the leftmost bit (i.e., msb = bit 1) and proceeding down to the rightmost bit of the sample (i.e., lsb = bit 8). on the other hand, data organized in n-bit words is transmitted serially starting with the rightmost bit (i.e., lsb = bit 0) and proceeding along to the left most bit (i.e., msb = bit n-1). cx28500 is designed to support the data transmission co nvention. that is, on the receive side, serial data is placed in the lsb of a word first up to the msb. on the trans mit side, the lsb (i.e., bit 0) is transmitted first, then on up to the msb. f.3 acronyms, abbreviations, and definitions f.3.1 acronyms and abbreviations the following is a list of acronyms used in this specification, and their expanded meanings. suffix example binary b 001011b hex h 6fh, 01bh decimal d 01d, 750d 23b+d twenty-three b channels plus one d channel 2b+d two b channels plus one d channel 2b1q two bits in one quaternary 30b+d thirty b channels plus one d channel
notation, acronyms, abbreviations, and definitions 28500-DSH-002-C mindspeed technologies ? 203 mindspeed proprietary and confidential ansi american national standards institute atm asynchronous transfer mode bam broadband access multiplexer chact channel activation chdeact channel deactivation cmos complementary meta l-oxide semiconductor cofa change of frame alignment cpu central processing unit crc cyclic redundancy code cts clear to send dce data communication equipment dma direct memory access dmi digital multiplexed interface ds0 digital signal?level zero (64 kbps) ds1 digital signal?level one (1.544 mbps) ds1c digital signal?level one c (3.152 mbps) ds2 digital signal?level two (6.312 mbps) ds3 digital signal?level three (44.736 mbps) dslam digital subscriber live access multiplexed dsx-1 digital signal cross-connect?level 1 (ds1) dsx-3 digital signal cross-connect?level 3 (ds3) dte data terminal equipment dxi data exchange interface e1 european transmission service at the e1 rate of 2.048 mbps ecc error correcting code eom end of message eos end of segment fcs frame check sequence fdl facilities data link fdm frequency division multiplexing fdma frequency division multiple access fep front-end processor fifo first-in first-out (memory) ft-1 fractional t-1 hdlc high-level data link control
notation, acronyms, abbreviations, and definitions 28500-DSH-002-C mindspeed technologies ? 204 mindspeed proprietary and confidential ic idle code ieee institute of electrical and electronic engineers isdn integrated services digital network islp intersystem link protocol itf interframe time fill itu international telecommunications union jtag joint test action group lan local area network lap-b link access protocol-balanced lap-d link access protocol-d lec local exchange carrier lsb least significant bit, or least significant byte m13 multiplexer between 28 ds1s and a ds3 mbps megabit per second msb most significant bit, or most significant byte mux multiplexer oc optical carrier oc-1 optical carrier?level 1 (51.84 mbps) oc-12 optical carrier?level 12 (622.08 mbps) oc-24 optical carrier?level 24 (1.244 gbps) oc-3 optical carrier?level 3 (155.52 mbps) oc-48 optical carrier?level 48 (2.488 gbps) odsx optical digital signal cross-connect oof out of frame osi open system interconnection pbx private branch exchange pci peripheral component interface (bus) pcm pulse code modulation pm performance monitoring ppp point-to-point protocol pri primary rate interface psn packet switched network rsiu receive serial interface unit rt remote terminal rx receive
notation, acronyms, abbreviations, and definitions 28500-DSH-002-C mindspeed technologies ? 205 mindspeed proprietary and confidential sdh synchronous digital hierarchy slp serial line processor smds switched multi-megabit data service sonet synchronous optical network sonet frame payload (data) plus overhead (control) spe synchronous payload envelope ss7 signalling system 7 ste section terminating equipment stm-1 synchronous transport multiplex (155.52 mbps) sts synchronous transport signal sts-1 synchronous transport signal ? level 1 (51.84 mbps) sts-3 synchronous transport signal ? level 3 (155.52 mbps) sts-3c synchronous transport signal ? level 3 concatenated (155.52 mbps) t1 transmission service at the ds1 rate of 1.544 mbps t3 transmission service at the ds3 rate of 44.736 mbps tdm time division multiplexing te terminal equipment ts time slot tsbus time slot bus tsiu transmit serial interface unit tx transmit vpn virtual private network vsp virtual serial port vt virtual tributary vt-1.5 virtual tributary ? level 1.5 (1.728 mbps) vt-2 virtual tributary ? level 2 (2.304 mbps) vt-3 virtual tributary ? level 3 (3.456 mbps) vt-6 virtual tributary ? level 6 (6.912 mbps) vt6-n virtual tributary ? level 6 (n x 6.9 mbps) wan wide area network zbtsi zero byte time-slot interchange zcs zero code suppression
notation, acronyms, abbreviations, and definitions 28500-DSH-002-C mindspeed technologies ? 206 mindspeed proprietary and confidential f.3.2 definitions the following is the list of technical definitions used in this document: byte a group of 8 binary bits. a byte is exactly synonymous with an octet. channel a logical bit stream passed through cx28500. the transmit direction is defined as the path from host interface to serial port; the receive direction is defined as the path from serial port to host interface. the channel rate is configurable. channelized refers to a serial port configuration whereby the bit stream is logically partitioned into 8-bit time slots. frame synchronization is required and allows mapping of individual bits, time slots, or virtual serial ports (vsp) into logical channel s. this mode is synonymous to pcm highway. data path a data path is one communications channel (i.e., ds1, e1, vt1.5, vt2.0, c-11, c-12, unchannelized ds3, or unchannelized sts-1 signals). one data path occupies a fixed number of time slots at fixed locati ons in a time slot bus frame. descriptor a single dword (i.e., 32-bit) control structure that describes some attributes of a data block. digital level 1 signals the following digital level 1 signals are the channelized data paths transported over the payload tsbus: ds1, e1, vt1.5, vt2.0, c-11, and c-12. digital level 2 signals the following digital level 2 signals contain the channelized data paths that are extracted and then transported over the receive payload tsbus: ds2, e2, vtg, and tug-2. dword a group of 32 bits. cx28500 assumes that memory is organized as 32-bit words, as viewed through the pci interface. this term is equivalent to a dword which is used for historical reasons to refer to double 16-bit words. flag as defined in hdlc, an octet with the value 7eh. hdlc frame in the context of an hdlc bit stream, a frame is a packet of information delimited with 7e flags. this term can be used interchangeably with message or packet. the term frame in this context is different than a t1 or e1 frame. hyperchannel refers to the concatenation of multiple time slots into a single logical channel. idle code octet pattern used to fill t he time between the clos ing flag of one messa ge and the opening flag of the next message. cx28500 supports the following patterns: 7eh, ffh, and 00h. logical channel also called a virtual serial port (see vsp, below). message refers to an hdlc frame or packet as delimited by opening and closing 7eh flags. octet synonymous with byte. refers to an association of 8 bits. pointer a single word (i.e., 32-bit) control structure that serves as an address to another word (i.e., word-aligned pointer) or byte (i.e., byte-aligned pointer). port one of the 32 full-duplex serial interfaces supported by cx28500. spe synchronous payload envelope. this is the envelope used within an sts frame structure to carry the path layer overhead and payload data in the sonet system. structure a general term referring to one or more data structures stored in shared memory. subchannel a portion of a 64 bp s time slot. that is, when a time slot is split and utilized as one sub-64 bps channel, it is referred to as subchannel. time slot an 8-bit portion of a t1 or e1 frame that repeats every 125 s, for a total of 64 kbps.
notation, acronyms, abbreviations, and definitions 28500-DSH-002-C mindspeed technologies ? 207 mindspeed proprietary and confidential tsbus time slot (ts) bus. the time slot bus is a time division multiplexed serial (one bit wide) connection for passing digital communication signals (data paths) between tbus device (broadband access multiplexer) and cx28500 (hdlc controller). tsbus frame a tsbus contains 84 time slots. unchannelized refers to a serial port configuration whereby the bit stream is considered a continuous stream delimited only by occasional overhead bits. no frame synchronization is required, only overhead bit identification. this port can be utilized only as a single logical channel. vc virtual container. this is the sdh equivalent term to spe. however, it applies to all digital signal levels. it contains payload bytes plus path overhead bytes. the vc contains one c-11 signal (which has 27 bytes and carries a ds1 si gnal or a non-ds1 signal) plus path overhead or one c-12 signal (which has 36 bytes and carries and e1 signal or a non-e1 signal) plus path overhead. vsp virtual serial port. a vsp is the multiple number of time slots that carry one data path in the transmit or in the receive tsbus frames. vt virtual tributary. a virtual tributary contains payload bytes plus pointer bytes in sonet systems. the two virtual tributaries referred to in this specification are: vt1.5 which has 27 bytes and carries a ds1 signal or a non-ds1 signal; vt2.0 which has 36 bytes and carries an e1 signal or a non-e1 signal. vtg virtual tributary group. a virtual tributary group consists of 108 bytes. one vtg carries 4 time multiplexed vt1.5?s signals or it carries 3 time multiplexed vt2.0 signals. one vtg does not carry both signals. word a word is a unit of data in general. usually it refers to 16-bits, but many times it is used more loosely to mean a single unit of data.
28500-DSH-002-C mindspeed technologies ? 208 mindspeed proprietary and confidential appendix g: scope of specification this document specifies the cx28500 input/output interfaces and the basic functionality of the device. g.1 applicable specifications the following is a list of specifications that provide backup information, or definition of standards that apply to cx28500.  pci local bus specification, revision 2.1, production version, june 1, 1995  ansi t1.408-1990  ccitt recommendation g.704  ieee standard 1149.1-1990  cx28478/8474a/8472a data sheet  topaz specification  pandora specification  cx28398 data sheet
www.mindspeed.com general information: telephone: (949) 579-3000 headquarters - newport beach 4000 macarthur blvd., east tower newport beach, ca 92660 ? 2006 mindspeed technologies ? , inc. all rights reserved. information in this document is provided in connection with mindspeed technologies ? ("mindspeed ? ") products. these materials are provided by mindspeed as a service to its customers and may be used for informational purposes only. except as provided in mindspeed?s terms and conditions of sale for such products or in any separate agreement related to this document, mindspeed assumes no liability whatsoever. mindspeed assumes no responsibility for errors or omission s in these materials. mindspeed may make changes to specifications and product descriptions at any time, without notice. mindspeed makes no commitment to update the information and shall have no responsibility whatsoever for conflicts or incom patibilities arising from future changes to its specifications and product descriptions. no license, ex press or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. these materials are provided "as is" withou t warranty of any kind, either express or implied, relating to sale and/or use of mindspeed products including liability or warranties relating to fitness for a particular purpose, consequential or incidental damages, merchantability, or infringement of any patent, copyright or other intellectual property right. mindspeed further does not warrant the accuracy or completeness of the information, text, graph ics or other items contained within these materials. mindspeed shall not be liable fo r any special, indirect, incidental, or consequential damages, including without li mitation, lost revenues or lost profits, which may result from the use of these materials. mindspeed products are not intended for use in medical, lifesaving or life sustaining applications. mindspeed customers using or selling mindspeed pr oducts for use in such applications do so at their own risk and agree to fully indemnify mindspeed for any damages resulting from such improper use or sale. 28500-DSH-002-C mindspeed technologies ? 209 mindspeed proprietary and confidential


▲Up To Search▲   

 
Price & Availability of 28500-DSH-002-C

All Rights Reserved © IC-ON-LINE 2003 - 2022  
[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]
 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X